We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think I observed that a forcepush, which aborts a build, kills the running job, but not others associated with the build.
I conclude this problem from the following error message of an aborted build:
debian Job cancelled (it could sucessfully clone and partially run the job) arch Chantal failed; stdout: Traceback (most recent call last):, File "/home/openage/chantal/__main__.py", line 32, in main, build_job(args), File "/home/openage/chantal/build.py", line 40, in build_job, run_command("git checkout -q " + args.commit_sha, base_env), File "/home/openage/chantal/util.py", line 46, in run_command, raise RuntimeError("command failed: %s [%d]" % (cmd, retval)), RuntimeError: command failed: git checkout -q 54024bf525232a4426ffb46c5d48a0304624fc41 [128], git checkout -q 54024bf525232a4426ffb46c5d48a0304624fc41 fatal: reference is not a tree: 54024bf525232a4426ffb46c5d48a0304624fc41 command returned 128 internal error
-> It tried cloning a non-existing git reference which was force-pushed away.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I think I observed that a forcepush, which aborts a build, kills the running job, but not others associated with the build.
I conclude this problem from the following error message of an aborted build:
-> It tried cloning a non-existing git reference which was force-pushed away.
The text was updated successfully, but these errors were encountered: