On 04/02/2020 09:41, Christian Holler wrote:
One of the problems with deploying ThreadSanitizer in CI is that we have a fair amount of existing data races that orange pretty much every test we have. In order to solve this situation, we are currently working on the following strategy:1. Add a Linux TSan build as Tier1 to avoid build regressions (done in bug 1590162 <https://bugzilla.mozilla.org/show_bug.cgi?id=1590162>) 2. Run a set of tests and generate a runtime suppression list <https://searchfox.org/mozilla-central/source/mozglue/build/TsanOptions.cpp> for all of the existing issues.
Which set of tests are we planning to run? If it includes web-platform-tests (which I imagine it should in order to get good coverage), we also need a strategy to handle importing tests which show previously unknown races, without turning jobs orange (in practice this means having some annotation in the relevant ini file and code to update the annotation based on wptreport logs).
_______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
