-
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: switch appveyor to gce builders to try debugging the 259 failure #58597
Conversation
@bors: r+ p=1 |
📌 Commit 703e236 has been approved by |
⌛ Testing commit 703e236 with merge fe5d50bfc845534a7c3f9a40aefb5eab82862465... |
💔 Test failed - checks-travis |
The job 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 |
I'm sure we didn't regress travis. @bors retry |
⌛ Testing commit 703e236 with merge 7437e36cc2a1c40fe75c6b3fd25160a0facb900b... |
💔 Test failed - checks-travis |
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 |
ci: switch appveyor to gce builders to try debugging the 259 failure r? @alexcrichton
☀️ Test successful - checks-travis, status-appveyor |
r? @alexcrichton