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
example: https://storage.googleapis.com/cp2k-ci/run-cp2k-sdbg-cf9d8f09_report.txt
This seems to happen when the master gets an update while the CI already started the job.
master
At least in 2017 using the /merge ref was an undocumented feature not meant to be used by 3rd parties.
/merge
The text was updated successfully, but these errors were encountered:
Yes, this sometimes happens. It should however be fairly rare and you can always hit re-run.
Currently, I have three ideas for fixing this:
I don't really like any of them.
the /merge ref was an undocumented feature not meant to be used by 3rd parties.
The merge branch is not well documented but it gets mention e.g. here. And I'm pretty sure most other CI system use it as well.
Sorry, something went wrong.
oschuett
No branches or pull requests
example: https://storage.googleapis.com/cp2k-ci/run-cp2k-sdbg-cf9d8f09_report.txt
This seems to happen when the
master
gets an update while the CI already started the job.At least in 2017 using the
/merge
ref was an undocumented feature not meant to be used by 3rd parties.The text was updated successfully, but these errors were encountered: