Investigate Arcade failures for version 5.0.0-beta.20221.14

Arcade Validation run: https://dnceng.visualstudio.com/internal/_build/results?buildId=612731&view=results

Runtime

Runtime build with this version of Arcade: https://dev.azure.com/dnceng/internal/_build/results?buildId=612845&view=results

LKG build used for this branch: https://dev.azure.com/dnceng/internal/_build/results?buildId=611275&view=results

Issues

• SourceLink Validation failure. Problem did not occur in LKG. A bunch of 404s from GitHub. Based on discussion down-thread, it sounds like this is a completely normal error to see based on how we’re handling the branching and running of this code (branch from GitHub, push to AzDO to run)

ASPNETCore

ASPNETCore build with this version of Arcade: https://dev.azure.com/dnceng/internal/_build/results?buildId=612842&view=logs&j=1b89928a-2219-5ef9-602f-f95beb3da4dc&t=39263dad-2be6-5f40-bde4-1bab0d7931b4&l=852

LKG build used for this branch: https://dev.azure.com/dnceng/internal/_build/results?buildId=612274&view=logs&j=1b89928a-2219-5ef9-602f-f95beb3da4dc&t=39263dad-2be6-5f40-bde4-1bab0d7931b4

Issues

• Warnings are being treated as errors. This was investigated and the mitigation around this is the following: By removing treatWarningsAsErrors from the override properties list, it’s now getting pulled in from Directory.Build.props. Avoid setting this property to true in Directory.Build.props for the impacted project, since it’s not actually able to restore without warnings.

[missymessa]

@safern @riarenas and I chatted about this and it sounds like this is expected based on how we’re handling… okay, Ricardo commented while I was in the middle of writing this 😃

[riarenas]

We branch from Github, but we only push the branch to AzDO. You’re right that this is normal.