Javascript:Automation Builds: Difference between revisions

Javascript:Automation Builds (view source)

106 bytes added , 18 May 2018

→‎SM(tsan): make this a little scarier

Confirmed users

328

edits

Revision as of 16:30, 18 May 2018 (view source) Sfink (talk \| contribs) (→‎SM(tsan): replace old tsan info) ← Older edit		Revision as of 16:38, 18 May 2018 (view source) Sfink (talk \| contribs) (→‎SM(tsan): make this a little scarier) Newer edit →
Line 44:		Line 44:
	sm-tsan uses the clang ThreadSanitizer dynamic thread safety checker. Since this is a dynamic analysis, any given run may report only a subset of issues based on the exact timing of that run. One thing that means is that failures in this job may well be intermittent, and thus may not be due to the immediately preceding push. You may consider retriggering a failure a few times to see what to blame it on.		sm-tsan uses the clang ThreadSanitizer dynamic thread safety checker. Since this is a dynamic analysis, any given run may report only a subset of issues based on the exact timing of that run. One thing that means is that failures in this job may well be intermittent, and thus may not be due to the immediately preceding push. You may consider retriggering a failure a few times to see what to blame it on.

	ThreadSanitizer failures are generally not security~~-critical~~, though they can be.		ThreadSanitizer failures are generally not security sensitive, though they can be. The usual rules apply -- eg if it's in GC code, it should be assumed to be sensitive until investigated.