-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
release-1.10
: set VERSION
to 1.10.0-alpha1
#50420
Conversation
Okay, that worked. I guess Buildkite doesn't want to run on #50394 because #50394 was created before the |
Just so you're aware, there's some discussion in #49805 about a potential issue with a previous PR feature-wise, that would be resolved with that PR (that just didn't seem to get merged before the feature freeze..) |
@nanosoldier |
@nanosoldier |
This is just an alpha so it basically provides no guarantees. |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. |
@DilumAluthge, what was the reason for rerunning nanosoldier? It's already running on the previous PR. |
Your package evaluation job has completed - possible new issues were detected. |
Ah, I just assumed that when the old PR was closed, it would auto-cancel the Nanosoldier job. (Similar to how when you delete a branch, Buildkite auto-cancels the CI run on that branch.) |
Replaces #50394
Closes #50394