701766 - Determine which tegras should not be on this list or find bugs associated to them

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Armen [:armenzg]]

http://build.mozilla.org/builds/last-job-per-slave.html is kind of cluttered with the tegra slaves.

I would like to determine which of these slaves should not be in our configuration files (if any) and which bugs track bring any of these slaves back.

tegra-001                310 days, 13:18:35
tegra-002                298 days, 9:34:32
tegra-003                308 days, 14:48:19
tegra-004                301 days, 16:33:25
tegra-005                304 days, 17:35:26
tegra-006                303 days, 20:27:45
tegra-007                310 days, 10:13:54
tegra-008                296 days, 20:38:29
tegra-009                297 days, 3:42:20 
tegra-010                325 days, 20:52:13 
tegra-011                239 days, 18:29:52 
tegra-012                239 days, 18:53:58 
tegra-013                240 days, 7:09:40 
tegra-014                239 days, 18:11:43 
tegra-015                240 days, 11:49:35 
tegra-016                132 days, 18:28:23 
tegra-017                231 days, 21:22:54 
tegra-018                240 days, 9:40:54  
tegra-019                24 days, 8:54:01  
tegra-020                106 days, 22:08:42
tegra-021                231 days, 21:18:24
tegra-022                No jobs yet 
tegra-023                14 days, 0:04:40  
tegra-024                231 days, 21:17:39 
tegra-025                13 days, 20:12:01  
tegra-026                132 days, 10:10:05 
tegra-027                153 days, 20:20:36 
tegra-028                28 days, 17:29:04  
tegra-029                13 days, 23:13:19  
tegra-030                132 days, 10:30:23 
tegra-045                133 days, 0:03:34  
tegra-053                176 days, 18:08:15  
tegra-055                133 days, 9:53:13    
tegra-058                No jobs yet 
tegra-060                123 days, 9:29:12 
tegra-069                29 days, 17:20:59 
tegra-071                40 days, 14:51:14 
tegra-086                8 days, 7:05:13    
tegra-098                29 days, 21:12:37  
tegra-103                22 days, 5:28:50   
tegra-116                29 days, 16:30:44 
tegra-122                No jobs yet 
tegra-123                No jobs yet 
tegra-124                No jobs yet 
tegra-125                No jobs yet 
tegra-126                No jobs yet 
tegra-127                No jobs yet 
tegra-128                No jobs yet 
tegra-131                No jobs yet 
tegra-137                No jobs yet 
tegra-143                No jobs yet 
tegra-147                No jobs yet 
tegra-149                9 days, 5:47:56   
tegra-152                No jobs yet

Comment 1

[Aki Sasaki (not active)]

tegra-001 through 030 are staging, so don't run on test-master01.

Comment 2

[Armen [:armenzg]]

Attachment: remove first 30 tegras from production

Comment 3

[Armen [:armenzg]]

Comment on attachment 573925 [details] [diff] [review]
remove first 30 tegras from production

http://hg.mozilla.org/build/buildbot-configs/rev/e6a25d6810ae

Comment 4

[Aki Sasaki (not active)]

This landed in this morning's reconfig.

Comment 5

[Armen [:armenzg]]

These tegras have not yet taken a job. Are they supposed to be in the production list? do they exist?

tegra-122	No jobs yet	no jobs		
tegra-123	No jobs yet	no jobs		
tegra-124	No jobs yet	no jobs		
tegra-125	No jobs yet	no jobs		
tegra-126	No jobs yet	no jobs		
tegra-127	No jobs yet	no jobs		
tegra-128	No jobs yet	no jobs		
tegra-131	No jobs yet	no jobs		
tegra-137	No jobs yet	no jobs		
tegra-143	No jobs yet	no jobs		
tegra-147	No jobs yet	no jobs		
tegra-161	No jobs yet	no jobs		
tegra-173	No jobs yet	no jobs		
tegra-174	No jobs yet	no jobs		
tegra-175	No jobs yet	no jobs		
tegra-176	No jobs yet	no jobs		
tegra-177	No jobs yet	no jobs

Comment 6

[Mike Taylor [:bear]]

those just now came online today - they should all be getting jobs by tomorrow

Comment 7

[Armen [:armenzg]]

(In reply to Mike Taylor [:bear] from comment #6)
> those just now came online today - they should all be getting jobs by
> tomorrow

I checked today and none of these slaves have been able to take a job.

Comment 8

[Mike Taylor [:bear]]

(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #5)
> These tegras have not yet taken a job. Are they supposed to be in the
> production list? do they exist?
> 

loaned to developers
> tegra-124	No jobs yet	no jobs		
> tegra-125	No jobs yet	no jobs		
> tegra-126	No jobs yet	no jobs		
> tegra-127	No jobs yet	no jobs		
> tegra-128	No jobs yet	no jobs		

on bob's bench being looked at	
> tegra-122	No jobs yet	no jobs		
> tegra-123	No jobs yet	no jobs		
> tegra-131	No jobs yet	no jobs		
> tegra-137	No jobs yet	no jobs		
> tegra-143	No jobs yet	no jobs		
> tegra-147	No jobs yet	no jobs	
> tegra-161	No jobs yet	no jobs	

on foopy17 but not started - fixed	
> tegra-173	No jobs yet	no jobs		
> tegra-174	No jobs yet	no jobs		
> tegra-175	No jobs yet	no jobs		
> tegra-176	No jobs yet	no jobs		
> tegra-177	No jobs yet	no jobs

Comment 9

[Armen [:armenzg]]

Attachment: remove tegras that have not yet taken a job

awesome. Thanks for the info.

On one side, I think if we added fake entries for tegras on slave-alloc we would be able to add notes to it (at least from last-job-per-slave.html would give some background info on the tegras). I'm going to go ahead and file a bug for it; sounds good?

bear, in this bug I remove the tegras from our production config files until these tegras come back to production_config.py.

On another note, tegra-173 to tegra-117 have not yet picked up a job in case you needed to know. Would you like me to not remove these slaves since there seem to be coming back soon? Do you have a bug tracking the fooppy issue?

Comment 10

[Mike Taylor [:bear]]

Comment on attachment 575867 [details] [diff] [review]
remove tegras that have not yet taken a job

do you need to to also adjust preproduction_config and staging_config ?

Comment 11

[Mike Taylor [:bear]]

(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #9)
> Created attachment 575867 [details] [diff] [review] [diff] [details] [review]
> remove tegras that have not yet taken a job
> 
> awesome. Thanks for the info.
> 
> On one side, I think if we added fake entries for tegras on slave-alloc we
> would be able to add notes to it (at least from last-job-per-slave.html
> would give some background info on the tegras). I'm going to go ahead and
> file a bug for it; sounds good?
> 
> bear, in this bug I remove the tegras from our production config files until
> these tegras come back to production_config.py.
> 
> On another note, tegra-173 to tegra-117 have not yet picked up a job in case
> you needed to know. Would you like me to not remove these slaves since there
> seem to be coming back soon? Do you have a bug tracking the fooppy issue?

no need for a tracking bug - I just forgot to start them last friday - fixed

Comment 12

[Armen [:armenzg]]

Comment on attachment 575867 [details] [diff] [review]
remove tegras that have not yet taken a job

Landed on "default":
http://hg.mozilla.org/build/buildbot-configs/rev/992edbddb9cc

I excluded range 173 to 177 as they are coming back.