-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New branch never finds ancestor commit #38
Comments
This Orb was working perfectly for many weeks and has stopped working all of a sudden. All of our builds are now failing because it cannot find the ancestor commit. Any idea why that would start happening? |
I have the same problem with version 1.0.0 of the orb. The only workaround to this is doing an empty commit or a dummy commit. |
I've fixed this issue and another issue so maybe you guys can use my fork for temporary.
|
I'm having the same issue (stuck in a loop), tried out @oshimayoan's fork but same results. |
@johnallen3d Could you share a snippet of your |
hmm thanks for the prompt @oshimayoan! I looked more closely at the output and noticed an error job -25068 was part of the current workflow, part of a rerun workflow, a retry of a previous job, or from a different branch
----------------------------------------------------------------------------------------------------
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 15166 100 15166 0 0 462k 0 --:--:-- --:--:-- --:--:-- 462k
sh: missing ]] Looking around here I see that this is a known issue when using an Alpine based container. #18 |
"fixed" the |
No probs! Does the orb work after you fixed the |
Works like a charm, thanks again! |
Orb version
1.2.0
What happened
After creating a new branch in our monorepo, compare-url Reconstruct step never finds an ancestor commit. It will loop all the way to CircleCI job 1. The full logs from the are pasted here: https://gist.githubusercontent.com/kennyjwilli/2474bcc03bff5039e465bd3d036de8b8/raw/c101f1825f5aec1d5b0a17058519c9e7141f8b31/log.txt.
Expected behavior
It should have found an ancestor commit.
The text was updated successfully, but these errors were encountered: