Closed
Bug 708346
Opened 13 years ago
Closed 12 years ago
android and android-xul test results are all reported as 'android'
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
Details
we need to differentiate between android and android-xul. I know specifically in our talos code and upload to the graph server. I imagine this needs to get fixed in log parsers as well as woo.
Comment 1•13 years ago
|
||
If this is problematic, the fastest short term solution would probably be to turn off android-xul tests until this is fixed longer term.
Comment 2•13 years ago
|
||
Oh, hey, bug 708341.
Reporter | ||
Comment 3•13 years ago
|
||
ack, so this is a graph server issue since we upload the machine name (i.e. 'tegra-314') and that maps to info about that machine including the os. http://hg.mozilla.org/graphs/file/tip/sql/data.sql#l1778: insert into machines values (NULL,20,0,1.0,"tegra-001",1,unix_timestamp()); the value of 20 is the os_id from here: http://hg.mozilla.org/graphs/file/tip/sql/schema.sql#l2 and 20 is defined here: http://hg.mozilla.org/graphs/file/tip/sql/data.sql#l20 So we either need to split the tegras we have into android and android-xul boxes (bad idea), or fix the graph server to resolve this. I am not sure of the best method to do that, maybe an additional piece of information when we are uploading that specifies the platform otherwise defaults to that of the sql tables.
Comment 4•13 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #3) > So we either need to split the tegras we have into android and android-xul > boxes (bad idea), or fix the graph server to resolve this. I am not sure of > the best method to do that, maybe an additional piece of information when we > are uploading that specifies the platform otherwise defaults to that of the > sql tables. Having a way to optionally override the platform name sounds fine, I'll file a graphserver bug and make it block this one.
Reporter | ||
Comment 5•12 years ago
|
||
we have a solution in place.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•