-
Notifications
You must be signed in to change notification settings - Fork 347
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
SDL verification job failure #5220
Comments
See something similar in arcade but with the build stage - https://dnceng.visualstudio.com/internal/_build/results?buildId=592226&view=results |
Another similar one:
|
This one is probably due to an import error in the sdl script: https://github.com/dotnet/arcade/blob/master/eng/common/sdl/extract-artifact-packages.ps1#L32 |
This one is weird. Due the error description:
I'm inclined to think this was a configuration problem in the build agent. |
@adiaaida @chcosta any ideas on the "## error NETCORE_ENGINEERING_TELEMETRY=Sdl" errors? |
Without digging in, I agree with @JohnTortugo assessment |
The Write-Host command not found issue has only occured in one out of 594 builds for aspnetcore, and is very much a machine configuration issue. This build ran on an azure devops hosted pool so it isn't one of our build machines that we can try to get a repro. The Write-PipelineTelemetryError issue is an import issue with the scripts. It appears to be caused by another error that was partially swallowed somehow. I can see the tail end of a stack trace. It has also only ocured in one build. We should probably add some more logging to this step so we can see what actually happened. |
The Write-Host issue only happened once and is 100% caused by an issue on the AzDev hosted machines. If it happens again we can continue investigating. The Write-PipelineTelemetryError issue is actually covering up a different problem, its obscuring the actual error. I opened #5254 to make the logging better in error cases. This error has also only happened once. If it comes back we can investigate, but it is a distinct issue from the Write-Host one. |
We're seeing some failures during the extraction step of the SDL job:
For example: https://dev.azure.com/dnceng/internal/_build/results?buildId=590888&view=logs&j=7d9eef18-6720-5c1f-4d30-89d7b76728e9&t=4c19956c-5c86-5c24-85d7-25b7fad31d7f&l=13
The text was updated successfully, but these errors were encountered: