Add metadata for workload automation #100648
Conversation
dotnet-issue-labeler
bot
added
the
needs-area-label
joeloff
added
area-Workloads
joeloff
added
Servicing-approved
|
@joeloff were you planning to merge this before end of day? |
Hoping to so we could get the workload automation unblocked, but I'm not quite sure why all the library tests are failing as they should not be related to the workloads. |
|
@joeloff the libraries failures are known, and not your problem. https://dev.azure.com/dnceng-public/public/_build/results?buildId=630659&view=logs&j=9a5515a2-33bf-5680-e294-03cf4426280b&t=dae9b252-1692-5386-8bf9-deb520e61356&l=1010 looks like a bigger concern though, that one is not known to the system |
This seems like the issue, though again, this change isn't calling the command that's missing. Is that coming from mono.proj?
Seems to be coming from Line 466 in 457c7d5 Feels like there's something missing from the image or environment. |
|
@directhex @lewing This build failed with the same error on WASM leg: |
|
I think it's a flake earlier up the build:
So the emsdk install fails, and emcmake isn't present. |
|
i.e. your changes aren't to blame - it's an infra issue beyond our control. We probably want a "known issue" for this failure condition, though. |
|
/ba-g failure is known and has since been fixed |
Description
To automate VSDROP insertions from staging builds, we need to include some additional metadata that is difficult to obtain from staging builds, like the assembly file version that is used when versioning drop components.
Testing
Manually verified metadata against internal builds. Cannot be fully tested until we have a fully staged build and all the automation pipelines completed.