Closed
Bug 911237
Opened 11 years ago
Closed 11 years ago
TBPL support for ASAN tests
Categories
(Tree Management Graveyard :: TBPL, defect)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: RyanVM)
References
Details
Attachments
(2 files, 1 obsolete file)
6.82 KB,
patch
|
emorley
:
review+
|
Details | Diff | Splinter Review |
2.97 KB,
image/png
|
Details |
We're running tests for asan builds on a few branches now, so need them to show up properly on TBPL.
The builders are called e.g. "Ubuntu ASAN VM 12.04 x64 cedar opt test mochitest-other"
Assignee | ||
Comment 1•11 years ago
|
||
We're still running debug ASAN builds. Do we want to be doing that? It affects what I want to do here.
Assignee: nobody → ryanvm
Assignee | ||
Comment 2•11 years ago
|
||
Creates a new flavor for ASAN builds. The builds + tests will show on their own line similar to how opt, debug, and pgo do currently. Note that this only really supports opt builds correctly at the moment. My understanding is that we only be running opt builds on m-c. However, I do see debug builds running on cedar.
Decoder, do we need to worry about supporting debug ASAN or is opt sufficient?
Attachment #797958 -
Flags: review?(emorley)
Flags: needinfo?(choller)
Assignee | ||
Comment 3•11 years ago
|
||
Correction, the debug builds run on m-c as well.
Comment 4•11 years ago
|
||
(Waiting on the needinfo before reviewing :-))
Comment 5•11 years ago
|
||
The tests are only run on opt, and we do not need to care about tests on debug (also not in the future most likely, because it's too slow and doesn't make much sense in my opinion).
We do however have debug *builds* on m-c and that's also pretty important to keep.
Flags: needinfo?(choller)
Comment 6•11 years ago
|
||
(In reply to Christian Holler (:decoder) from comment #5)
> We do however have debug *builds* on m-c and that's also pretty important to
> keep.
Yeah comment 2 was meaning the debug builds - out of curiosity, what value do they add? :-)
Assignee | ||
Comment 7•11 years ago
|
||
Well, I feel dirty.
This works, but it's not as elegant as I was hoping. This:
1.) Creates a new ASan flavor
2.) Add new symbols for ASan debug/opt builds/nightlies
If we didn't have to support debug builds, we could just add the flavor and get rid of all the extra symbols. If we ran tests on debug builds, we could just add a debug ASan flavor to cover it all. However, since this is the world we live in, I think this solution makes the most sense.
Attachment #797958 -
Attachment is obsolete: true
Attachment #797958 -
Flags: review?(emorley)
Attachment #798125 -
Flags: review?(emorley)
Comment 8•11 years ago
|
||
(In reply to Ed Morley [:edmorley UTC+1] from comment #6)
> (In reply to Christian Holler (:decoder) from comment #5)
> > We do however have debug *builds* on m-c and that's also pretty important to
> > keep.
>
> Yeah comment 2 was meaning the debug builds - out of curiosity, what value
> do they add? :-)
The main reason for having them is that they use less inlining and therefore can produce more meaningful traces if the opt trace is not clear.
Comment 9•11 years ago
|
||
Fwiw, I would be ok with just showing ASan opt on TBPL and leave the debug build in the hidden job, if it's too much of a hassle to get both :)
Assignee | ||
Comment 10•11 years ago
|
||
It really doesn't matter whether it's visible by default or not. We still need to display it in a sensible way when it is shown.
Comment 11•11 years ago
|
||
What I meant is that it could remain part of this job:
https://tbpl.mozilla.org/?jobname=asan&showall=1
But maybe I am misunderstanding something here.
Assignee | ||
Comment 12•11 years ago
|
||
The patch as attached creates a new "Linux64 ASAN" line where all builds + tests are displayed rather than intermingling them on other lines.
Mainly I'm concerned about the visual consistency of displaying all of the opt jobs in a line by themselves while putting the debug build on a different line. Default visibility doesn't really impact that one way or the other. I think showing both Opt and Debug like the attached picture makes the most sense.
And if we some day want to run tests on debug builds, we can just remove the "Bo/Bd" special casing and add another "Linux64 ASAN Debug" flavor instead.
Comment 13•11 years ago
|
||
Comment on attachment 798125 [details] [diff] [review]
create new ASAN flavor
Review of attachment 798125 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good - only tweak I might suggest is to swap opt and debug around (just in config.js), so it displays as Bo Bd (ie same order as the opt/debug rows do themselves :-)
Attachment #798125 -
Flags: review?(emorley) → review+
Assignee | ||
Comment 14•11 years ago
|
||
Comment 15•11 years ago
|
||
In production :-)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 16•11 years ago
|
||
I can see the builds here
https://tbpl.mozilla.org/?showall=1
but not the tests. Am I missing something?
Assignee | ||
Comment 17•11 years ago
|
||
They're running on Cedar, not m-c.
Comment 18•11 years ago
|
||
This bug was just to get TBPL to identify the ASan tests properly, which it now does:
https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=asan
However, it looks like there was a problem with the patches in bug 831491 to get the jobs to run on other trees, since they have been checked in (and more importantly merged to production and presumably reconfiged) but the jobs aren't appearing.
Updated•10 years ago
|
Product: Webtools → Tree Management
Updated•10 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•