900782 - (tegra-119) tegra-119 problem tracking

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Description

[Ryan VanderMeulen [:RyanVM]]

Frequently hitting "application ran for longer than allowed maximum time" errors running Armv6 reftests. In general, seems to take 30-35min longer to run them than their counterparts.

Comment 1

[Pete Moore [:pmoore][:pete]]

I've disabled this tegra, by creating file:

[[e-mail] ~]$ touch /builds/tegra-119/disabled.flg

watch_devices.sh running on this foopy should bring it down shortly - let me know if there are any problems!

Thanks,
Pete

Comment 2

[Justin Wood (:Callek)]

Banking on a reimage recovering it. Once it is we'll need to re-enable it in slavealloc though.

Comment 3

[Chris Cooper [:coop] (he/him)]

Re-enabled in slavealloc.

Comment 4

[Van Le [:van]]

SD card replaced, tegra reimaged and flashed.

[[e-mail]3 ~]$ fping tegra-119.tegra.releng.scl3.mozilla.com
tegra-119.tegra.releng.scl3.mozilla.com is alive

Comment 5

[Jordan Lund (:jlund)]

this machine is back in production and greening

although when I:

[[e-mail] builds]$ ./check.sh -t tegra-119
04/04/2014 14:24:36: INFO:  Tegra ID M    Tegra       CP    Slave :: Msg
2014-04-04 14:24:36,505  Tegra ID M    Tegra       CP    Slave :: Msg
04/04/2014 14:24:42: INFO: tegra-119 p    online   active  OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts] 
2014-04-04 14:24:42,529 tegra-119 p    online   active  OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts] 

callek: so I learn, why does it say there is an error.flg on it. and that it is unable to connect?

I am resolving since:

- I can't see error.flg in /builds/tegra-119
- slavehealth says it's doing green jobs
- /builds/tegra-119/twistd.log says it recently took a job
- slavealloc says it's enabled

I

Comment 6

[Jordan Lund (:jlund)]

re: https://bugzilla.mozilla.org/show_bug.cgi?id=900782#c5