Bootstrap builds should use ExitingTraceListener
The bootstrap builds of the compiler today are using the default trace listener which presents a dialog. That means when a `Debug.Assert` call fires we end up hanging the build in Azure. The intent was always for the bootstrap builds to use the `ExitingTraceListener`. This way they exit with a crash and call stack that allows the compiler team to diagnose the failure. The behavior of `Debug.Assert` showing a dialog is the most likely explanation for our current random hangs in the determinism leg. That is the only place we still use a `DEBUG + BOOTSTRAP` build. The symptoms line up. If that's the case this will start showing us the stack trace of the assert.
Showing
想要评论请 注册 或 登录