Closed Bug 462891 Opened 16 years ago Closed 16 years ago

need a stack or access to one of the linux talos machines on the tracemonkey tree

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: sayrer, Assigned: joduinn)

Details

We have an intermittant crash that we cannot reproduce, after much effort.
This blocks the beta, because we don't know what it is. It went away over the weekend, but reappeared this morning.
In bug#461020, we already gave mrbkap access to a talos slave - is that access not enough?
(In reply to comment #2)
> In bug#461020, we already gave mrbkap access to a talos slave - is that access
> not enough?

Unfortunately no, this is only occurring on linux, and mrbkap got access to a mac talos machine.

I changed the platform of this bug to linux, though the bug title was always correct.
OS: Mac OS X → Linux
Does this problem reproduce on try talos, like bug#461020 did? I ask because its less risky for us to open up access on the try talos linux slave...
(In reply to comment #4)
> Does this problem reproduce on try talos, like bug#461020 did? I ask because
> its less risky for us to open up access on the try talos linux slave...

errr... any update? Does this reproduce on try talos?
Just discovered (and repaired) a problem where the two linux slaves on try server were suspended and not accepting new jobs. Now repaired, and the two slaves are going through the queued pending jobs.

If any of these queued jobs reproduce the problem, please let us know, and we'll take that specific slave out of production, so you can debug.
Assignee: nobody → joduinn
Any success here ?

Is this bug still needed or can I close?
No response in bug, or to private emails. Closing as INCOMPLETE. Please reopen if this is still an issue.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.