Closed
Bug 935246
Opened 13 years ago
Closed 12 years ago
Graphserver doesn't know how to handle the talos results from non-PGO builds on the B2G release branches
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Unassigned)
References
Details
Bug 932962 turned off PGO for all browser builds on the B2G release branches. However, graphserver is now erroring out when trying to send talos results.
What I would like to do is land the b2g26 patch in bug 927512 to kill off OSX and Windows talos (as has already been done for b2g18*). Then we will need to add support to graphserver for Linux32/Linux64 non-PGO results from these branches.
| Reporter | ||
Comment 1•13 years ago
|
||
Actually, the linux32 and linux64 talos runs on b2g26 appear to be green, so apparently this only affects Windows. Assuming that's the case for b2g18* as well, that means we only need to fix the Windows b2g26 case.
Summary: Graphserver doesn't know how to handle the talos results from non-PGO builds on the B2G release branches → Graphserver doesn't know how to handle the talos results from Windows non-PGO builds on the B2G release branches
| Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #1)
> Assuming that's the case for b2g18* as well, that means we only need to fix the Windows b2g26 case.
Which of course will be fixed by the second patch in bug 927512.
| Reporter | ||
Comment 3•13 years ago
|
||
Looking at the logs, Linux32 and Linux64 are indeed having the same problem, but for some reason they are reported to TBPL as passing anyway (sounds like another bug to me). So we'll still need a graphserver fix for the Linux jobs even when Windows is disabled.
Summary: Graphserver doesn't know how to handle the talos results from Windows non-PGO builds on the B2G release branches → Graphserver doesn't know how to handle the talos results from non-PGO builds on the B2G release branches
| Reporter | ||
Comment 4•12 years ago
|
||
Linux32 and Linux64 are indeed burning on b2g18*. Not sure why they aren't on b2g26.
Comment 5•12 years ago
|
||
What are the names it's complaining about?
| Reporter | ||
Comment 6•12 years ago
|
||
Mozilla-B2g26-v1.2-Non-PGO
Mozilla-B2g18-Non-PGO
And whatever the v1.1hd version of that is.
Comment 7•12 years ago
|
||
mysql> insert into branches (`name`) values ('Mozilla-B2g26-v1.2-Non-PGO'), ('Mozilla-B2g18-Non-PGO'), ('Mozilla-B2g18-v1.1.0hd-Non-PGO');
Query OK, 3 rows affected (0.00 sec)
Records: 3 Duplicates: 0 Warnings: 0
| Reporter | ||
Comment 8•12 years ago
|
||
Working now, thanks!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 9•12 years ago
|
||
catlee: there should be a corresponding patch made to http://hg.mozilla.org/graphs/file/b61e7261ca4b/sql/data.sql as well
Flags: needinfo?(catlee)
Updated•12 years ago
|
Flags: needinfo?(catlee)
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•