Closed
Bug 1227310
Opened 10 years ago
Closed 10 years ago
Funny release-mode buildids in derived stream
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: benjamin, Assigned: trink)
Details
Looking at the release derived stream, I'm seeing a collection of funny buildids:
["2015082600 ", "2015091800 ", "2015092900 ", "2015101500 ", "2015103000 "]
These buildIDs have a significant amount of data attached to them, so it's not complete random flukes. I have a couple questions:
* are the trailing spaces coming from the derived stream process? Or are there padding spaces in the original data?
* Are these Linux disto builds? I'm a little surprised that they are reporting to the release channel. I'd be very worried if these were Mozilla builds but less worried if this is coming in via distros.
Updated•10 years ago
|
Assignee: nobody → mtrinkala
Priority: -- → P1
| Assignee | ||
Comment 1•10 years ago
|
||
The ones I looked at are all Linux in the release channel. They have a length of 10 (however the buildid is character(14) which is fixed-length, blank padded). This also produces some unexpected results but is working as designed.
pipeline=# select char_length(buildid), buildid, buildid || 'x' from crash_summary_20151130 where buildid ~ ' $' limit 10;
char_length | buildid | ?column?
-------------+----------------+-------------
10 | 2015103000 | 2015103000x
10 | 2015103000 | 2015103000x
...
pipeline=# select count(*) from crash_summary_20151130 where buildid = '2015103000';
count
-------
892
(1 row)
pipeline=# select count(*) from crash_summary_20151130 where buildid = '2015103000 ';
count
-------
892
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•