Homebrew has once again decided that it would be amusing to start failing 100% of the time starting on the day before the beta release day.
See https://dev.azure.com/coq/coq/_build/results?buildId=13834&view=logs&j=a5e52b91-c83f-5429-4a68-c246fc63a4f7&t=7d499b5d-1d92-5096-7919-3c7f8065da78, https://github.com/coq/coq/pull/13587#issuecomment-739783217 and https://dev.azure.com/coq/coq/_pipeline/analytics/stageawareoutcome?definitionId=1 (for the stats).
If some Homebrew user wants to help debug and fix this, we'll be grateful!
Can we reset the VMs? it seems it is the clean phase of homebrew that fails
which I imagine can be avoided by starting afresh
BTW, who has the rights to log in azure?
Also, this time it did work: https://github.com/coq/coq/pull/13580 (the only difference is the version printed by Coq)
401 - Uh-oh, you do not have access.
This is using my personal account on "microsoft"
@Gaëtan Gilbert @Maxime Dénès do you have access to the admin interface of azure?
Eh eh, if I log in with github I get
We're unable to complete your request Microsoft account is experiencing technical problems. Please try again later.
I think Azure retrieves the list of users with some level of access to the GitHub repo (I don't know if it's write-access or admin-access), so it's important to log in with GitHub indeed.
If you are logged in, can you check if the machines can be cleared (as in travis' "cache" thing).
The log says "brew clean did not run in the last 30 days"...
there must be some state
No way, it seems login via gihub does not work for me
I don't see any state on azure
I've disabled brew cleanup and it seems to continue the build fine now
I guess it's fine for v8.13, not sure for master
Last updated: Dec 06 2023 at 14:01 UTC