Closed
Bug 1131742
Opened 10 years ago
Closed 10 years ago
buildjson data is missing information about cedar
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: armenzg, Unassigned)
References
Details
Attachments
(2 files)
There were a lot of jobs that were run for "cedar" on the 6th:
https://secure.pub.build.mozilla.org/buildapi/self-serve/cedar/rev/2f13b2f9b088
However, I can't see any buildernames for cedar in the associated buildjson files.
Any thoughts?
armenzg@armenzg-thinkpad:~/moz/tmp$ wget http://builddata.pub.build.mozilla.org/builddata/buildjson/builds-2015-02-06.js.gz
--2015-02-10 14:58:29-- http://builddata.pub.build.mozilla.org/builddata/buildjson/builds-2015-02-06.js.gz
Resolving builddata.pub.build.mozilla.org (builddata.pub.build.mozilla.org)... 63.245.215.57
Connecting to builddata.pub.build.mozilla.org (builddata.pub.build.mozilla.org)|63.245.215.57|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 21737657 (21M) [text/plain]
Saving to: ‘builds-2015-02-06.js.gz’
100%[===================================================================================================================================================================>] 21,737,657 3.30MB/s in 6.3s
2015-02-10 14:58:35 (3.31 MB/s) - ‘builds-2015-02-06.js.gz’ saved [21737657/21737657]
armenzg@armenzg-thinkpad:~/moz/tmp$ gzip -d builds-2015-02-06.js.gz
armenzg@armenzg-thinkpad:~/moz/tmp$ grep 'cedar' builds-2015-02-06.js | wc -l
0
armenzg@armenzg-thinkpad:~/moz/tmp$ grep 'cypress' builds-2015-02-06.js | wc -l
61
|
Reporter | |
Comment 1•10 years ago
|
||
For some reason, it is missing for only some days:
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-05.js
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-06.js
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-08.js
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-09.js
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-07.js | wc -l
7923
|
||
Comment 2•10 years ago
|
||
were there builds on those other days?
|
|
Reporter | |
Comment 3•10 years ago
|
||
Nevermind that last comment.
The 6th still applies.
For some reason we have data on the 7th (even if there were no builds); how can that be explained?
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(catlee)
|
|
Reporter | |
Comment 5•10 years ago
|
||
Thanks catlee. I will look into it and close this.
I will look into using what I find in here:
http://mxr.mozilla.org/build/source/buildapi/buildapi/lib/helpers.py
|
|
Reporter | |
Comment 6•10 years ago
|
||
The cedar case reported above was fixed by clobbering my local js file and fetching it again.
I don't know what happened there.
armenzg@armenzg-thinkpad:~/repos/ci_tools$ grep "cedar" builds-2015-02-09.js | wc -l
1213
I'm now investigating another instance I have.
A job run for _mozilla-inbound_ on 02-09 appears on the 02-10.js file.
I wil be looking at repoter.py shortly to see if I figure this out.
At the moment I can't figure out why the job would show up on 02-10 when all time stamps are pointing to 02-09.
NOTE:I'm using pacific_time() everywhere.
From build-02-10.js (shorter version of [2])
"endtime": 1423539926, --> Mon, 09 Feb 2015 19:45:26 -0800 (PST)
...
"buildername": "WINNT 5.2 mozilla-inbound build",
"buildid": "20150209184600",
...
"got_revision": "0f4fc6a418ed",
...
"request_times": {
"61522815": 1423536361 --> Mon, 09 Feb 2015 18:46:01 -0800 (PST)
},
"revision": "0f4fc6a418ed71564195cde9979d7588688515a5",
"requesttime": 1423536361, --> Mon, 09 Feb 2015 18:46:01 -0800 (PST)
"starttime": 1423536390 --> Mon, 09 Feb 2015 18:46:30 -0800 (PST)
}
[1]
From https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-inbound/build/62643009
{
"build_id": 62643009,
"buildnumber": 3532,
"status": 0,
"starttime": 1423536391, --> Mon, 09 Feb 2015 18:46:31 -0800 (PST)
...
"claimed_at": 1423539530, --> Mon, 09 Feb 2015 19:38:50 -0800 (PST)
...
"buildid": "20150209184600",
...
"complete_at": 1423539928, --> Mon, 09 Feb 2015 19:45:28 -0800 (PST)
"priority": 0,
"submittime": 1423536361,
"branch": "integration/mozilla-inbound",
"request_id": 61522815,
"revision": "0f4fc6a418ed71564195cde9979d7588688515a5"
}
],
"endtime": 1423539928, --> Mon, 09 Feb 2015 19:45:28 -0800 (PST)
"claimed_by_name": "buildbot-master86.srv.releng.scl3.mozilla.com:/builds/buildbot/build1/master",
"revision": "0f4fc6a418ed71564195cde9979d7588688515a5"
}
[2]
From 02-10.js
{
"builder_id": 198325,
"buildnumber": 3532,
"endtime": 1423539926,
"id": 58650934,
"master_id": 104,
"properties": {
"appName": "Firefox",
"appVersion": "38.0a1",
"basedir": "/c/builds/moz2_slave/m-in-w32-000000000000000000000",
"branch": "mozilla-inbound",
"buildername": "WINNT 5.2 mozilla-inbound build",
"buildid": "20150209184600",
"buildnumber": 3532,
"builduid": "9aeaf05aba1d4e4cb21fc87a9c5962d6",
"comments": "Bug 1128420 - remove finished output streams from MediaDecoder::mOutputStreams. r=roc.",
"commit_titles": [
"Bug 1128420 - remove finished output streams from MediaDecoder::mOutputStreams. r=roc."
],
"got_revision": "0f4fc6a418ed",
"jsshellUrl": "http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1423536360/jsshell-win32.zip",
"log_url": "http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1423536360/mozilla-inbound-win32-bm86-build1-build3532.txt.gz",
"master": "http://buildbot-master86.srv.releng.scl3.mozilla.com:8001/",
"packageUrl": "http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1423536360/firefox-38.0a1.en-US.win32.zip",
"platform": "win32",
"product": "firefox",
"project": "",
"repo_path": "integration/mozilla-inbound",
"repository": "",
"request_ids": [
61522815
],
"request_times": {
"61522815": 1423536361
},
"revision": "0f4fc6a418ed71564195cde9979d7588688515a5",
"scheduler": "mozilla-inbound-firefox",
"script_repo_revision": "e8bb8fd6cb6b",
"script_repo_url": "https://hg.mozilla.org/build/mozharness",
"slavename": "b-2008-ix-0122",
"sourcestamp": "0f4fc6a418ed",
"stage_platform": "win32",
"symbolsUrl": "http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1423536360/firefox-38.0a1.en-US.win32.crashreporter-symbols.zip",
"testsUrl": "http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1423536360/firefox-38.0a1.en-US.win32.tests.zip",
"toolsdir": "/c/builds/moz2_slave/m-in-w32-000000000000000000000/scripts",
"uploadFiles": "[u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.zip', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/install/sea/firefox-38.0a1.en-US.win32.installer.exe', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/win32/xpi/firefox-38.0a1.en-US.langpack.xpi', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.tests.zip', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.crashreporter-symbols.zip', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.txt', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.json', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/firefox-38.0a1.en-US.win32.mozinfo.json', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/jsshell-win32.zip', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/host/bin/mar.exe', u'c:/builds/moz2_slave/m-in-w32-000000000000000000000/build/src/obj-firefox/dist/host/bin/mbsdiff.exe']"
},
"reason": "scheduler",
"request_ids": [
61522815
],
"requesttime": 1423536361,
"result": 0,
"slave_id": 8887,
"starttime": 1423536390
}
|
|
Reporter | |
Comment 7•10 years ago
|
||
I think I _might_ have been having this issue because I'm now looking at jobs that did not get run on the same day.
If I push today, I will find my jobs in 2015-02-12 (date == today scenario).
If I pushed on the 09th, I should look at that date + 1, the 10th (date != today scenario).
[ ] builds-2015-02-09.js.gz 10-Feb-2015 00:02 19M
[ ] builds-2015-02-10.js.gz 11-Feb-2015 00:03 24M
[ ] builds-2015-02-11.js.gz 12-Feb-2015 00:25 25M
[ ] builds-2015-02-12.js.gz 12-Feb-2015 13:16 15M (date == today scenario)
|
|
Reporter | |
Comment 8•10 years ago
|
||
|
|
Reporter | |
Comment 9•10 years ago
|
||
On a specific buildjson day file, we include all jobs that ended within the same time based on UTC.
That means 4pm PDT from the day before to 4pm of the same day (e.g. 4pm Jan. 9th to 4pm Jan. 10th).
Different times of the year the 4pm will change, however, the UTC times are invariable.
|
|
Reporter | |
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
|
Assignee | |
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•