need foopy + 5 new tegras to test resolution changes

RESOLVED FIXED

Status

defect
RESOLVED FIXED
7 years ago
a year ago

People

(Reporter: jmaher, Assigned: Callek)

Tracking

Firefox Tracking Flags

(Not tracked)

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

Updated

7 years ago
Assignee: nobody → bugspam.Callek
Assignee

Updated

7 years ago
Depends on: 790816
Assignee

Comment 1

7 years ago
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?
Reporter

Comment 4

7 years ago
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?
Reporter

Updated

7 years ago
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
Last Resolved: 7 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
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.