Enable symbols for autoland linux builds to enable pernosco self-serve reproductions
Categories
(Firefox Build System :: Task Configuration, enhancement)
Tracking
(firefox87 fixed)
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: asuth, Assigned: mozilla)
Details
Attachments
(2 files, 1 obsolete file)
644.14 KB,
patch
|
Details | Diff | Splinter Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
It is quite common for failed landings on autoland to uncover failures that were not previously known. Pernosco has a documented mechanism for generating reproductions from taskcluster job failures of individual tests but they depend on the task having generated "target.crashreporter-symbols-full.EXTENSION" artifacts. Per discussion with :khuey this logic in taskcluster/taskgraph/transforms/build.py is the reason, only enabling the symbols for RELEASE_PROJECTS
and "try"
but not autoland.
This enabling would only be necessary for platforms supported by pernosco, which means linux64 I believe.
Assignee | ||
Comment 1•5 years ago
|
||
:gsvelto, as Crash Reporting module owner, are there are any concerns with turning on full crashreporter symbols on autoland?
Comment 2•5 years ago
|
||
As long as we don't upload them to the symbol server, the only concerns would be about artifact size on taskcluster's s3 and build times (although the latter shouldn't be too much of a concern).
Comment 3•5 years ago
|
||
Implementation-wise, adding MOZ_ENABLE_FULL_SYMBOLS: "1"
to the relevant tasks's environment variables in taskcluster/ci/build/linux.yml
should do it (that would also enable it on central, beta, release, etc. after it rides the train, but I don't see why it shouldn't).
Comment 4•5 years ago
|
||
From our perspective this is basically a cost/benefit tradeoff for Mozilla and whether it's worth the cost of storing those files in s3.
Comment 5•5 years ago
|
||
Like Mike said if the symbols aren't uploaded to the symbol server then the only additional costs are for storage on S3. I don't have hard numbers about this, but given that the number of try builds should exceed autoland by a pretty large margin I guess the increase in storage requirements should be reasonable (especially given this is only for linux64).
Assignee | ||
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
https://phabricator.services.mozilla.com/D103818 appears to create an upload symbols task as well. Is that problematic?
Assignee | ||
Comment 8•5 years ago
|
||
This is the diff in the taskgraph between central and central-with-this-patch, using autoland parameters.
Updated•5 years ago
|
Comment 9•5 years ago
|
||
(In reply to Aki Sasaki [:aki] (he/him) from comment #7)
https://phabricator.services.mozilla.com/D103818 appears to create an upload symbols task as well. Is that problematic?
Yes, that will upload the symbols to the symbol server for every build.
Assignee | ||
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
bugherder |
Description
•