Skip to content
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

[ci] fatal: reference is not a tree #43

Open
dev-zero opened this issue May 29, 2019 · 1 comment
Open

[ci] fatal: reference is not a tree #43

dev-zero opened this issue May 29, 2019 · 1 comment
Assignees

Comments

@dev-zero
Copy link

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.

@oschuett
Copy link
Member

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:

  1. Perform the merge myself in run_target.sh and ci_entrypoint.sh.
  2. Backup the merge branch somewhere (different repo or different branch name)
  3. Add a detection and auto re-run mechanism in the backend.

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.

@oschuett oschuett transferred this issue from cp2k/cp2k May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants