Closed Bug 790685 Opened 12 years ago Closed 12 years ago

need foopy + 5 new tegras to test resolution changes

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jmaher, Assigned: Callek)

References

Details

(Whiteboard: reopen once foopy and tegras are no more needed) 

this will ensure that we can fix our reftest problem by not changing the resolution.
Assignee: nobody → bugspam.Callek
Depends on: 790816
cltbld@foopy26.build.mozilla.org

Has joel's pubkey on it, him or me can add clint's pubkey on demand.

I attached 5 new tegras on it, and they are currently running jobs from the buildbot staging master, when you're ready to manually run stuff just |screen -x| (to get into our screen session) then |./stop_cp.sh| to kill buildbot and the jobs

Finally `ps auxwww | grep tegra-` to verify that all processes relating to these are stopped.

Feel free to ask me/armen/kim if you need any releng help dealing with these.
Should this bug be passed to the a-team?
BTW do we have a bug to track the specific issue that we're seeing wrt to screen resolutions?
we have access to this setup, have found an easy to reproduce problem and need developers to help figure out what is going on.
Can we please have a bug to depend/block this on?
Depends on: 792212
No longer depends on: 790816
Thanks jmaher.

I think this bug is done wrt to giving access to foopies and tegras.
I assume we can close it and re-open once the foopy/boards are to be returned.

Please correct me if I got it wrong.
Status: NEW → RESOLVED
Closed: 12 years ago
Depends on: 790816
Resolution: --- → FIXED
Whiteboard: reopen once foopy and tegras are no more needed
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.