-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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: Move most builders to Azure Pipelines #62179
Conversation
56a24de
to
166b2f7
Compare
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=100 |
📌 Commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a has been approved by |
⌛ Testing commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a with merge 1983951a8b06e9586c75c30c9c5bb38f028f2272... |
💔 Test failed - checks-azure |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors: retry |
Is there a plan for an Azure-based replacement for this in-PR-tools-builder? It's been very useful, good to know that the checks pass in CI which can be hard or slow to do locally. Not a big deal though if that doesn't work any more or will need some more time to be fleshed out. :) |
⌛ Testing commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a with merge b4ada1a4756bdbc5552075dad58b99eb6b271246... |
💔 Test failed - checks-azure |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors retry |
⌛ Testing commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a with merge a97389087064e9ad75e6db0f58700fce5f0dc18b... |
@bors: treeclosed=99 |
⌛ Testing commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a with merge 8043df452e97b0a8b802bd8695b9ca254ad81a7d... |
💔 Test failed - checks-azure |
@bors: retry |
⌛ Testing commit 166b2f7b61e36d9aef04010b3dd18fa60be33b9a with merge 7319585e71b791017062cc471f325f924e0abf1e... |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors: treeclosed- |
💥 Test timed out |
This commit disables all builders on Travis and almost all builders on AppVeyor now that they're all running on Azure Pipelines. There is one remaining builder on AppVeyor which hasn't been migrated yet due to a test failure on Azure, which we'll be debugging soon. One remaining builder is left on Travis which is the tools builder whenever a submodule is changed, but we'll probably turn that off soon since it's just for PRs. The other major change in this PR is that the auto builders on Azure are now configured with "real" prod credentials which should cause them to publish all artifacts into the official CI buckets.
166b2f7
to
6f838b4
Compare
@bors: r=pietroalbini Leaving x86_64-gnu-tools entirely on travis as well due to the same RLS failure on Azure. Seems like a spurious test failure we'll have to deal with one way or another o Azure. |
📌 Commit 6f838b4 has been approved by |
ci: Move most builders to Azure Pipelines This commit disables all builders on Travis and almost all builders on AppVeyor now that they're all running on Azure Pipelines. There is one remaining builder on AppVeyor which hasn't been migrated yet due to a test failure on Azure, which we'll be debugging soon. One remaining builder is left on Travis which is the tools builder whenever a submodule is changed, but we'll probably turn that off soon since it's just for PRs. The other major change in this PR is that the auto builders on Azure are now configured with "real" prod credentials which should cause them to publish all artifacts into the official CI buckets.
☀️ Test successful - checks-azure, checks-travis, status-appveyor |
This commit disables all builders on Travis and almost all builders on
AppVeyor now that they're all running on Azure Pipelines. There is one
remaining builder on AppVeyor which hasn't been migrated yet due to a
test failure on Azure, which we'll be debugging soon. One remaining
builder is left on Travis which is the tools builder whenever a
submodule is changed, but we'll probably turn that off soon since it's
just for PRs.
The other major change in this PR is that the auto builders on Azure are
now configured with "real" prod credentials which should cause them to
publish all artifacts into the official CI buckets.