Closed
Bug 737895
(talos-r4-lion-035)
Opened 12 years ago
Closed 11 years ago
talos-r4-lion-035 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Unassigned)
References
Details
(Whiteboard: [buildduty])
It looks like this machine doesn't have its edid emulator plugged into it. This machine shows: talos-r4-lion-035:~ cltbld$ system_profiler SPDisplaysDataType Graphics/Displays: NVIDIA GeForce 320M: Chipset Model: NVIDIA GeForce 320M Type: GPU Bus: PCI VRAM (Total): 256 MB Vendor: NVIDIA (0x10de) Device ID: 0x08a4 Revision ID: 0x00a2 ROM Revision: 3546 talos-r4-lion-035:~ cltbld$ screenresolution get 2012-03-21 09:08:29.945 screenresolution[1325:707] starting screenresolution argv=screenresolution get 2012-03-21 09:08:29.952 screenresolution[1325:707] Display 0: 1280x1024x32 talos-r4-lion-035:~ cltbld$ screenresolution list 2012-03-21 09:08:32.931 screenresolution[1326:707] starting screenresolution argv=screenresolution list Available Modes on Display 0 1x1x8 1x1x16 1x1x32 1x1x64 1x1x96 800x600x8 800x600x16 800x600x32 800x600x64 800x600x96 1024x768x8 1024x768x16 1024x768x32 1024x768x64 1024x768x96 1280x1024x8 1280x1024x16 1280x1024x32 1280x1024x64 1280x1024x96 1680x1050x8 1680x1050x16 1680x1050x32 1680x1050x64 1680x1050x96 1280x1024x32 talos-r4-lion-035:~ cltbld$
Updated•12 years ago
|
Assignee: server-ops-releng → mlarrain
colo-trip: --- → scl1
Updated•12 years ago
|
Alias: talos-r5-lion-035 → talos-r4-lion-035
Assignee: mlarrain → jwatkins
Status: NEW → ASSIGNED
Summary: please reinsert the dongle on talos-r5-lion-035 → please reinsert the dongle on talos-r4-lion-035
Comment 1•12 years ago
|
||
I couldn't get the correct resolution with the edid101d that was attached so I swapped it with a spare. It is now getting the correct resolution with the new edid101d.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 2•12 years ago
|
||
https://secure.pub.build.mozilla.org/buildapi/recent/talos-r4-lion-035 chewing up jobs as fast as it can - the one I saw was 2012-06-15 14:27:12.636 hdiutil[4552:10b] error: unable to set up framework server. DIHLDiskImageAttach() returned 6 (null) hdiutil: attach failed - Device not configured
Assignee: jwatkins → nobody
Status: RESOLVED → REOPENED
Component: Server Operations: RelEng → Release Engineering: Machine Management
QA Contact: arich → armenzg
Resolution: FIXED → ---
Summary: please reinsert the dongle on talos-r4-lion-035 → talos-r4-lion-035 problem tracking
Updated•12 years ago
|
Whiteboard: [buildduty]
Comment 3•12 years ago
|
||
Restarted; green.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
Sneakily crashed in https://tbpl.mozilla.org/php/getParsedLog.php?id=20697407&tree=Services-Central, crc check failed in https://tbpl.mozilla.org/php/getParsedLog.php?id=20705169&tree=Mozilla-Inbound
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•11 years ago
|
||
Running; largely green.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 6•11 years ago
|
||
Hasn't done a job since May 28th.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 7•11 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
Timing out every time it attempts to run a b2g18 mochitest. These failures aren't being seen on any other slave. https://tbpl.mozilla.org/php/getParsedLog.php?id=24771823&tree=Mozilla-B2g18 https://tbpl.mozilla.org/php/getParsedLog.php?id=24772743&tree=Mozilla-B2g18 https://tbpl.mozilla.org/php/getParsedLog.php?id=24780626&tree=Mozilla-B2g18 https://tbpl.mozilla.org/php/getParsedLog.php?id=24790708&tree=Mozilla-B2g18
Comment 9•11 years ago
|
||
Disabled in slavealloc. Screenshots are a showing a Finder crash report dialog, fwiw.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•11 years ago
|
||
waiting on bringup process for talos-r4-lion. I also modified the puppet script so we stop sending humpty-dumpty errors about it
Comment 11•11 years ago
|
||
Testing with PuppetAgain in bug 891880.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 13•11 years ago
|
||
this specific machine is causing noise in talos results about once a day for the last week. I am not sure of the frequency or if this just gets the lucky set of cards each time, but it is odd that all wild outliers on tsvgx for 10.7.2 on inbound result from this specific machine. Is this pulled from slavealloc? As we have had problems with this for months on and off, maybe we could EOL this or give it to non 24x7 automation purposes.
Comment 14•11 years ago
|
||
A bit off topic, do we have a system in place which automatically tries to correlate outliers with specific machines?
Comment 15•11 years ago
|
||
That is one of the things we are working on for datazilla. We have noticed this problem more and more as we become aware of the problem either at the tbpl view or looking more into the data.
Comment 16•11 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #13) > this specific machine is causing noise in talos results about once a day for > the last week. I am not sure of the frequency or if this just gets the > lucky set of cards each time, but it is odd that all wild outliers on tsvgx > for 10.7.2 on inbound result from this specific machine. > > Is this pulled from slavealloc? As we have had problems with this for > months on and off, maybe we could EOL this or give it to non 24x7 automation > purposes. Let's run hardware diagnostics and reimage it, that often helps.
Comment 17•11 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•