-
Notifications
You must be signed in to change notification settings - Fork 640
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
Tag 8.13 beta1 #13587
Tag 8.13 beta1 #13587
Conversation
This was just based on observing how previous beta were handled when I wrote this. I'm not the expert on magic numbers though, so this could be a discussion to have with other Coq devs. |
It looks like we're doomed! Homebrew has chosen to start failing again on all PRs since yesterday 😱 See https://dev.azure.com/coq/coq/_pipeline/analytics/stageawareoutcome?definitionId=1 (this looks like a 100% failure rate today with 4 failures, all during this step). |
|
can we "reset" the workers on azure? I really don't know how these VMs are handled, but it seems that is the cleanup that fails |
I know very little about Azure. You have a whole bunch of settings that you can access here https://dev.azure.com/coq/coq/_settings/testmanagement after being logged in with GitHub though. To add to the doom, it looks like the Windows job is failing as well: https://coq.gitlab.io/-/coq/-/jobs/894114063/artifacts/artifacts/buildlogs/ocaml-4.08.1-make-flexdll_err.txt |
For windows we don't have the right job in CI yet. I can build it on my VM, and together with Michael we have been testing it, so it's OK. |
@Zimmi48 , but for the failures, is the PR OK? I'd like to merge and tag. |
Sure but you have another strategy to produce the macOS installer once this is tagged if we don't manage to fix the Azure failure without changing the configuration itself? (Like asking a Coq developer on macOS to produce the installer?) |
I have an installer build on azure that has the only difference in the contents of this PR (version number). So the scripts are not too broken. |
OSX is back on track |
This should be it.
It's not super clear what "We generally do not update the magic numbers at this point." means. In which case should I do that?