-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Restore failing on our projects #35057
Comments
@ViktorHofer this looks related to the static graph work. |
Is the stack trace always the same? If yes then cc @GrabYourPitchforks who renamed that project recently. |
Tagging subscribers to this area: @ViktorHofer |
For the ones I looked at yes these are all the same. That remnids me though that @safern and @GrabYourPitchforks had a post merge conflict yesterday. Possible this is just an artifact of that. |
That was my assumption as well. I'm fairly certain this was fixed with dd22ce8. Closing, feel free to reopen if this pops up again. |
Yeah that was closed with the commit @ViktorHofer pointed above. That was a fallout of the rename merged while my PR was open and had green builds and then when I merged it started failing. |
Gotcha. Looks like our CI just hasn't caught up with that yet |
Yeah. Note that all the PRs that were open in the timeframe of when the error was discovered and the PR with the merge was merged, will see this symptom unless they update with a push or rebase so that their builds have the fix, so that might be the reason why it still shows on those PRs. |
Failure from the restore
Evaluated 100 builds
Impacted 25 builds
Impacted 84 jobs
The text was updated successfully, but these errors were encountered: