CI: ratchet build warnings to errors now that the solution builds with 0 warnings (#725) #766
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since #725 the CI Release build of ZB.MOM.WW.OtOpcUa.slnx has 0 warnings. Add the ratchet the issue's last acceptance item asked for (e.g.
TreatWarningsAsErrorsfor test projects, or-warnaserrorin the CI build step) and update the stale comment in Directory.Build.props that says test projects aren't clean. Also review the xUnit1051 code-fix sites whereWriteAsync(..., default)became the runner token, in case a test relied on ignoring runner cancellation.Fixed on master
c904472a:TreatWarningsAsErrors=trueset globally in Directory.Build.props (the 61 src/ projects already set it per project since #606 — now extended to tests; stale comment rewritten); applies to CI too, so v2-ci.yml unchanged. Evidence:dotnet build ZB.MOM.WW.OtOpcUa.slnx -c Release -m:2 --no-incremental0 warnings / 0 errors, Debug clean; a planted unused local in a test project fails the build (CS0219). xUnit1051 code-fix review: the WriteAsync(..., default)→runner-token sites (MqttDriverWriteTests) and Task.Run(..., token) sites don't run cleanup/shutdown under the token or rely on ignoring cancellation — no further changes.