You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"ErrorMessage" : "The Operation will be canceled. The next steps may not contain expected logs.",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
}
@dotnet/dnceng
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
Additional information about the issue reported
No response
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=696281 Error message validated:[The Operation will be canceled. The next steps may not contain expected logs.] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 6/4/2024 8:08:48 PM UTC
These appear to be timeout cancellations, and most of them are happening on the same runtime leg that uses OSX.1200.ARM64.Open, looking at grafana, they do indeed appear to be quite high. Will check with the team on what we can do about this
There is also a number of Publish Using Darc timeouts, these are in 99% of cases AzDo Api issues. During the Publish Using Darc job, we queue up a Maestro Promotion pipeline, that downloads the artifacts from the build calling it, and publishes them where they need to go. While publishing is happening, the build pipeline keeps busy waiting for the promotion pipeline to be done, checking the status of it every 60 seconds. In cases where this times out, the build most likely did get promoted, the AzDo API just kept telling us the wrong thing
Build
https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=696281
Build leg reported
Build / browser-wasm linux Release LibraryTests / Send to Helix
Pull Request
dotnet/runtime#103009
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=696281
Error message validated:
[The Operation will be canceled. The next steps may not contain expected logs.
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/4/2024 8:08:48 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: