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)

x86
macOS
task
Not set
normal

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$
Assignee: server-ops-releng → mlarrain
colo-trip: --- → scl1
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
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
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
Whiteboard: [buildduty]
Restarted; green.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Running; largely green.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Hasn't done a job since May 28th.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back in production.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Disabled in slavealloc.

Screenshots are a showing a Finder crash report dialog, fwiw.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 889423
waiting on bringup process for talos-r4-lion.

I also modified the puppet script so we stop sending humpty-dumpty errors about it
Testing with PuppetAgain in bug 891880.
puppetagain errors showing bad screen resolution.
Depends on: 899065
Product: mozilla.org → Release Engineering
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.
A bit off topic, do we have a system in place which automatically tries to correlate outliers with specific machines?
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.
(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.
Depends on: 913087
Back in production.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.