Closed Bug 1513628 Opened 5 years ago Closed 2 years ago

AWSY try runs with DMD enabled on OSX timeout

Categories

(Testing :: AWSY, enhancement, P3)

Product:
Testing
Component:
AWSY
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: aryx, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1500523 +++

+++ This bug was initially created as a clone of Bug #1409739 +++

> See bug 1409739, comment 37. Currently AWSY with DMD enabled is only supported for try. It can be run with:

> ./mach try -b o -p macosx64 -u awsy-dmd-e10s

> The OSX test is permafail due to DMD reports timing out. This didn't seem like a huge deal when we landed but unfortunately it's run when people do an "all tests" push which has lead to a bit of confusion as to whether or not their changes are causing the failure.

> I think we want to do a few things here:

> #1 - We should probably disable the sy-d test for mac by default. We still want to be able to explicitly request it, just not have it include in '-p all' runs. Arguably we might just want to disable by default across the board.

> #2 - Fix the timeout issue. It's possible just bumping the timeout in nsMemoryReporterManager [1] is good enough, but it might be worth profiling to see what's going on. I suspect that symbol fixing [2] is the culprit.

> [1] https://searchfox.org/mozilla-central/rev/29aea2a2a3bd0f5e25ce0b60a76053fb25ba5149/xpcom/base/nsMemoryReporterManager.h#209
> [2] https://searchfox.org/mozilla-central/rev/29aea2a2a3bd0f5e25ce0b60a76053fb25ba5149/xpcom/base/CodeAddressService.h#148

Currently it's almost permafailing on OS X opt (saw only 1 green run), see e.g. https://treeherder.mozilla.org/#/jobs?repo=try&revision=559308a5a9fa94a788bda58e5f1a017440480966&searchStr=sy-d&selectedJob=216604479
Flags: needinfo?(erahm)
I've done about all I can with this. We have two options now:

#1 - Someone spends time figuring out why DMD runs are so slow on OSX and provides a fix / workaround (just extending the timeout was not enough)
#2 - we need someone who understands our tryserver and taskcluster to figure out how to prevent this from running by default.
Flags: needinfo?(erahm)

:mccr8, do you think this is still valid or should we close this?

Flags: needinfo?(continuation)

It might be valid, but I think we can close it for now unless it gets in the way of something specific.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(continuation)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.