Closed Winniexu01 closed 5 months ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Oh how ironic that the test is failing on itself 🤣
This is caused by the current work going onto consolidate the sdk and installer repos. The installer repo content currently was copied to the sdk recently which is why this just appeared. Today the source-build content is not scanned which is why this wasn't flagged before. This appears to be a gap.
Oh how ironic that the test is failing on itself 🤣
[Triage] This will be resolved when the sdk->installer merge is complete.
This was resolved with the sdk-installer merge.
main
build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2435523&view=logs&j=6743a87c-2e18-5ff9-0f6c-56bd82018320&t=6b957730-76c5-5b5b-c7fc-7fc79d5ee5c5More detail: scancode-results.json