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 for 9.0.1 is broken due to missing upstream commit #2016

Closed
isovector opened this issue Jul 13, 2021 · 3 comments · Fixed by #2017
Closed

CI for 9.0.1 is broken due to missing upstream commit #2016

isovector opened this issue Jul 13, 2021 · 3 comments · Fixed by #2017
Labels
CI Continuous integration type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc..

Comments

@isovector
Copy link
Collaborator

It appears CI for 9.0.1 is broken. At least four PRs currently in the queue are broken in 9.0.1 with the following error:

Cloning into '/home/runner/work/haskell-language-server/haskell-language-server/dist-newstyle/src/operation_-2cf41f8926150174'...
fatal: reference is not a tree: 0e062895678f49fd673ae493371262cfb8c5ab56

Digging in, that commit appears to be referenced here:

- github: berberman/operational
commit: 0e062895678f49fd673ae493371262cfb8c5ab56
# https://github.com/HeinrichApfelmus/operational/pull/26

and comes with a helpful PR reference:

HeinrichApfelmus/operational#26

which is now merged. Looking at the commit in question:

berberman/operational@0e06289

github responds with

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

which sounds scary and I'd bet is why CI is failing.

@berberman your name is attached to the commit in question, mind investigating?

@jneira
Copy link
Member

jneira commented Jul 13, 2021

The problem is the branch in berberman's repo was deleted after merge so the commit does not exist anymore. We have to change the commit to point to HeinrichApfelmus/operational/master, as the pr was merged into

@berberman
Copy link
Collaborator

Sorry, my bad, I should've kept my branch even if the PR was merged.

@isovector
Copy link
Collaborator Author

This is the sort of thing nobody would ever think about :) No worries at all!

@mergify mergify bot closed this as completed in #2017 Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc..
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants