* [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't
@ 2022-12-31 10:53 steinex
2022-12-31 14:20 ` classabbyamp
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: steinex @ 2022-12-31 10:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
New issue by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.1_1 x86_64 AuthenticAMD notuptodate hold rrrmDFFFFFFFFFFF
### Package(s) Affected
no specific package
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/steinex/void-packages/pull/230
https://github.com/steinex/void-packages/pull/227
### Expected behaviour
CI should run as usual.
### Actual behaviour
To check if my package builds for all archs, I always open a PR on my own branch first for QA. This stopped working with the problem:
```
Error: Your branch is too out of date. Please rebase on upstream and force-push.
Error: Process completed with exit code 1.
```
This does only happen on my own branch, if I push directly to void-packages everything is fine.
### Steps to reproduce
1. Prepare a PR
2. Push to own branch
3. See CI failing
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
@ 2022-12-31 14:20 ` classabbyamp
2022-12-31 14:43 ` steinex
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2022-12-31 14:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368221717
Comment:
is the master branch on your fork up-to-date with the master branch of the main repo?
you could also try running parts of this script manually locally: https://github.com/void-linux/void-packages/blob/master/common/travis/changed_templates.sh
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
2022-12-31 14:20 ` classabbyamp
@ 2022-12-31 14:43 ` steinex
2022-12-31 14:43 ` steinex
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: steinex @ 2022-12-31 14:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
New comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563
Comment:
Yes, the master branch of my fork is up-to date. The script you mentions gives nothing besides
```
Changed packages:
```
So I assume that means there are no changed between my fork and master.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
2022-12-31 14:20 ` classabbyamp
2022-12-31 14:43 ` steinex
@ 2022-12-31 14:43 ` steinex
2022-12-31 14:44 ` steinex
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: steinex @ 2022-12-31 14:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
New comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563
Comment:
Yes, the master branch of my fork is up-to date. The script you mention gives nothing besides
```
Changed packages:
```
So I assume that means there are no changed between my fork and master.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (2 preceding siblings ...)
2022-12-31 14:43 ` steinex
@ 2022-12-31 14:44 ` steinex
2022-12-31 14:49 ` classabbyamp
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: steinex @ 2022-12-31 14:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
New comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563
Comment:
Yes, the master branch of my fork is up-to date. The script you mention gives nothing besides
```
Changed packages:
```
So I assume that means there are no changes between my fork and master.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (3 preceding siblings ...)
2022-12-31 14:44 ` steinex
@ 2022-12-31 14:49 ` classabbyamp
2023-01-04 22:10 ` Chocimier
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2022-12-31 14:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368225218
Comment:
hm not in a spot to debug this atm but it appears to be cloning your fork as the master branch and the pr branch so that shouldn't be an issue. maybe someone else can find the issue
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (4 preceding siblings ...)
2022-12-31 14:49 ` classabbyamp
@ 2023-01-04 22:10 ` Chocimier
2023-01-07 12:51 ` classabbyamp
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Chocimier @ 2023-01-04 22:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1371488873
Comment:
changed_templates.sh uses FETCH_HEAD, which after full clone is set to random branch rather than master
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (5 preceding siblings ...)
2023-01-04 22:10 ` Chocimier
@ 2023-01-07 12:51 ` classabbyamp
2023-01-08 18:59 ` steinex
2023-01-10 23:07 ` [ISSUE] [CLOSED] " classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2023-01-07 12:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 220 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1374471176
Comment:
maybe switching that line to `git merge-base master "$tip"` would work?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (6 preceding siblings ...)
2023-01-07 12:51 ` classabbyamp
@ 2023-01-08 18:59 ` steinex
2023-01-10 23:07 ` [ISSUE] [CLOSED] " classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: steinex @ 2023-01-08 18:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
New comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1374903776
Comment:
> maybe switching that line to `git merge-base master "$tip"` would work?
I gave this a try. Unfortunately it didn't change anything.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ISSUE] [CLOSED] CI on own fork always fails because the branch is out of date albeit it isn't
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
` (7 preceding siblings ...)
2023-01-08 18:59 ` steinex
@ 2023-01-10 23:07 ` classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2023-01-10 23:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Closed issue by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.1_1 x86_64 AuthenticAMD notuptodate hold rrrmDFFFFFFFFFFF
### Package(s) Affected
no specific package
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/steinex/void-packages/pull/230
https://github.com/steinex/void-packages/pull/227
### Expected behaviour
CI should run as usual.
### Actual behaviour
To check if my package builds for all archs, I always open a PR on my own branch first for QA. This stopped working with the problem:
```
Error: Your branch is too out of date. Please rebase on upstream and force-push.
Error: Process completed with exit code 1.
```
This does only happen on my own branch, if I push directly to void-packages everything is fine.
### Steps to reproduce
1. Prepare a PR
2. Push to own branch
3. See CI failing
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-01-10 23:07 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-31 10:53 [ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't steinex
2022-12-31 14:20 ` classabbyamp
2022-12-31 14:43 ` steinex
2022-12-31 14:43 ` steinex
2022-12-31 14:44 ` steinex
2022-12-31 14:49 ` classabbyamp
2023-01-04 22:10 ` Chocimier
2023-01-07 12:51 ` classabbyamp
2023-01-08 18:59 ` steinex
2023-01-10 23:07 ` [ISSUE] [CLOSED] " classabbyamp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).