-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: debug azure timeouts #43611
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: debug azure timeouts #43611
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
arm failure is ok if you merge master |
Sounds good. Sorry, should've marked this as draft - want to let CI run a few times because I added |
Thanks for taking the lead on this. Looks like its one of the mac builds that timed out this last time. |
But no timeout was detected :( |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Logs from a timeout: https://dev.azure.com/pandas-dev/e01c9671-576d-40f3-a1a1-7bef78604087/_apis/build/builds/66368/logs/77
Just goes quiet for 30 min, can't think of anything around the tests running there that would cause this. Wonder if timeout shows up same place every time |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hmm latest timeout looks to have |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@mzeitlin11 still active here? |
Closing for now - anyone is welcome to reopen and run some pipelines if seeing lots of azure timeouts |
More attempts to see what's causing the timeouts.