You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The microsoft internal HLSL ADO pipeline has been getting spurious test failures in the clangd unit tests. These don't seem to be happening on any public bots and they don't seem to be reproducible on individuals' local machine setups.
We need to carve out some time to investigate and figure out what to do. This could involve trying to reproduce the problem and debug it, fiddling with settings in the bot to see if we can get more information, reaching out to external folks to see if anyone is aware of similar issues, or attempting to disable or automatically flag the failures as inactionable.
The failures are recognizable as a failure in the clangd unit tests that doesn't tend to have a proper error message. They are not always in the same test. Sometimes accompanied by un-symbolized backtraces like so:
The microsoft internal HLSL ADO pipeline has been getting spurious test failures in the clangd unit tests. These don't seem to be happening on any public bots and they don't seem to be reproducible on individuals' local machine setups.
We need to carve out some time to investigate and figure out what to do. This could involve trying to reproduce the problem and debug it, fiddling with settings in the bot to see if we can get more information, reaching out to external folks to see if anyone is aware of similar issues, or attempting to disable or automatically flag the failures as inactionable.
The failures are recognizable as a failure in the clangd unit tests that doesn't tend to have a proper error message. They are not always in the same test. Sometimes accompanied by un-symbolized backtraces like so:
The text was updated successfully, but these errors were encountered: