-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Builds legs getting abandoned due to agent notification issues #35223
Comments
Using runfo, in the last 200 builds, I'm seeing 2 instances of this - from April 14 and April17.
Unfortunately, the logs from these builds are gone and there is nothing to investigate. Do you have additional examples or should we consider this issue closed (until we see new instances)? /cc @ViktorHofer |
Are you sure about that? Because the top post says: > Most recent failure 5/7/2020 1:12:00 AM |
@ilyas1974 try taking out the |
Similar results -
Do you have any additional suggestions? |
Something isn't right here. I'm taking a look. |
Okay figured this out. There are two sources of confusion here:
To work around the second issue I added a new argument to
|
Thank you @jaredpar. I have created https://github.com/dotnet/core-eng/issues/9801 for our FR team to take a look and see what we can determine about these failures. |
Did some more searching and I found pretty much every variant of this. Essentially builds that hit this on first attempt, latest attempt and for some attempt in the middle. That's not surprising on one hand but it does really mean that probably need expanded search capabilities for certain issues. Have a tweak available locally where I can say |
We're seeing less of these failures and received an update from core-eng regarding a new date when the AzDO transition should be complete. See https://github.com/dotnet/core-eng/issues/9448 for more details. |
Yes they're different problems.
|
Closing as not observable anymore. |
Full message
Runfo Tracking Issue: Runtime jobs being abandoned due to infra
Build Result Summary
The text was updated successfully, but these errors were encountered: