CI reporting core dumps present after (passing) interop tests
Categories
(NSS :: Test, defect)
Tracking
(Not tracked)
People
(Reporter: kjacobs, Unassigned)
Details
Attachments
(1 obsolete file)
Sometime over the weekend, NSS taskcluster workers started failing the interop task due to core files existing after the run. The tests themselves all pass, and a local run doesn't reproduce the issue.
My suspicion is that the workers started pulling a new file that triggers the core detection, but this needs to be investigated further.
Reporter | ||
Comment 1•4 years ago
|
||
When building tls_interop, rustc by default produces output that enables incremental builds. I don't know what the naming scheme is for these files (the names seem mostly garbled), but they're producing a substring of "core" on CI, which looks like a core dump to the test script.
interop.sh already calls //detect_core// to add similar files from OpenSSL to an "allowlist". This doesn't work here, because cargo run
(and incremental build output) occurs later.
Since we never need to rebuild here, the fix is to just disable incremental output.
Reporter | ||
Comment 2•4 years ago
|
||
These failures have stopped occurring on their own (maybe the date is an input to the file naming scheme?)
Either way, unless this shows up again we probably don't need to land any changes.
Updated•4 years ago
|
Comment hidden (Intermittent Failures Robot) |
Description
•