Closed
Bug 797388
Opened 12 years ago
Closed 12 years ago
Borrow a linux test machine to debug unittest failures
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rcampbell, Assigned: rcampbell)
References
Details
(Whiteboard: [buildduty])
We have a bunch of test failures related to webgl on linux. We're tracking these failures in bug 759157, but are at an impasse with what we can do without access to the machines. It could be driver-related. It could be hardware. We just don't know.
Can we borrow one to do some testing please? Thanks!
Updated•12 years ago
|
Whiteboard: [buildduty]
Assignee | ||
Comment 1•12 years ago
|
||
Is there an ETA on this?
Comment 3•12 years ago
|
||
talos-r3-fed-002 loaned. Please reassign it to nobody once you're done with the slave. Password sent.
Assignee: rail → rcampbell
Blocks: talos-r3-fed-002
Comment 4•12 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #2)
> I'm going to assign one within a couple of hours.
Thank you so much for this!
Comment 5•12 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #3)
> talos-r3-fed-002 loaned. Please reassign it to nobody once you're done with
> the slave. Password sent.
I'll require build-vpn access as well to optimize the debugging process on those failures. Is that ok Rail?
Comment 6•12 years ago
|
||
(In reply to Victor Porof [:vp] from comment #5)
> (In reply to Rail Aliiev [:rail] from comment #3)
> > talos-r3-fed-002 loaned. Please reassign it to nobody once you're done with
> > the slave. Password sent.
>
> I'll require build-vpn access as well to optimize the debugging process on
> those failures. Is that ok Rail?
Is the BuildVPN access still needed? (I'm on duty this week)
Comment 7•12 years ago
|
||
(In reply to Armen Zambrano G. [:armenzg] from comment #6)
>
> Is the BuildVPN access still needed? (I'm on duty this week)
That would be swell!
Comment 8•12 years ago
|
||
Credentials have been emailed to Victor.
NOTE: We still need bug 802117 to be resolved before you can have access.
Comment 9•12 years ago
|
||
(In reply to Rob Campbell [:rc] (:robcee) from comment #0)
> We have a bunch of test failures related to webgl on linux. We're tracking
> these failures in bug 759157, but are at an impasse with what we can do
> without access to the machines. It could be driver-related. It could be
> hardware. We just don't know.
>
> Can we borrow one to do some testing please? Thanks!
This bug has now been resolved - Rob, presume you no longer have a need for this slave? :-)
Comment 10•12 years ago
|
||
(In reply to Ed Morley (PTO/travelling until 24th Oct) [:edmorley UTC+1] from comment #9)
> (In reply to Rob Campbell [:rc] (:robcee) from comment #0)
> This bug has now been resolved - Rob, presume you no longer have a need for
> this slave? :-)
It may be wise to keep it around for another week, in case the oranges start being chatty again, but I don't feel strongly about it.
Assignee | ||
Comment 11•12 years ago
|
||
if it doesn't hurt us to hang onto it for another week, then let's keep it. Otherwise, return it to the pool whence it originated!
Comment 12•12 years ago
|
||
(In reply to Ed Morley [:edmorley UTC+0] from comment #9)
The failures stopped occurring, it's fine to let the slave do its thing now :)
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•