sec
Verbose logs during building
Hey @sec and @Thefrank
The dotnet port fails on some occasions when building on FreeBSD cluster due to 7200 timeout rule: https://pkg-status.freebsd.org/beefy22/data/140amd64-default/50625859d806/logs/dotnet-8.0.6.log
Is it possible to make the build more verbose thus avoiding triggering this failure? I tried passing various flags to MSBuild, but didn't get desired behavior when a line is printed for each file being compiled.
The TASK.binlog file is debug level of verbose. Inspect that if you have access to it. Otherwise -v diag should give diagnostic level of logging in most cases for dotNET.
edit: all source build infrastructure creates .log files that should be in the artifacts/logs path
edit2: that stage should not take more than 1hr. Something else my have gone wrong.
Those kind of timeout also I had - mainly it was becuase of crossgen2 issues, also on aarch64 it's libunwind bug in newest release, but can't recall if I had those on amd64 lately :/
The TASK.binlog file is debug level of verbose. Inspect that if you have access to it. Otherwise -v diag should give diagnostic level of logging in most cases for dotNET.
I need logs to be printed on the console. Passing -v:diag to build.sh does indeed increase amount of stuff printed, but it is still printed at the beginning/end of each component's build. While building a component nothing is printed.
edit2: that stage should not take more than 1hr. Something else my have gone wrong.
FreeBSD cluster builds a lot of packages in parallel and only use one CPU core for each package. It may also starve for I/O throughput, so it might well possible for build taking a lot of time.
Re-routed this issue upstream: https://github.com/dotnet/arcade/issues/16038