Closed Bug 926868 Opened 12 years ago Closed 12 years ago

gofaster is not refreshing since end of september

Categories

(Testing Graveyard :: GoFaster, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glandium, Assigned: emorley)

References

Details

Attachments

(1 file)

No description provided.
The date suggests that gofaster is using http://build.mozilla.org for its data, as that was taken down on Sept 30 (bug 604688).
Dustin, what should the new URL be? I can't seem to find it at my inital secure.oub.m.o guesses...? :-) That csv is output here: http://mxr.mozilla.org/build-central/source/braindump/reports/buildfaster_report.sh#9
Blocks: 604688
Flags: needinfo?(dustin)
build.m.o is no more, the csv now resides at: http://builddata.pub.build.mozilla.org/reports/buildfaster.csv.gz Once this is checked in, happy for me to push to prod on brasstacks? Presuming I just pull the repo there?
Assignee: nobody → emorley
Status: NEW → ASSIGNED
Attachment #817811 - Flags: review?(wlachance)
Comment on attachment 817811 [details] [diff] [review] Update csv source to builddata.pub.build.m.o Review of attachment 817811 [details] [diff] [review]: ----------------------------------------------------------------- Looks good. One minor suggestion. ::: bin/fetch-and-process-builddata.sh @@ +17,5 @@ > esac > done > > if [ $LOCAL == 0 ]; then > + wget http://builddata.pub.build.mozilla.org/reports/buildfaster.csv.gz -O - | gunzip > $CSV_OUTPUT So, in retrospect it might have been better to make the location a define at the top of the file like: BUILDDATA_LOCATION=http://builddata.pub.build.mozilla.org/reports/buildfaster.csv.gz then just: wget $BUILDDATA_LOCATION -O - | gunzip > $CSV_OUTPUT
Attachment #817811 - Flags: review?(wlachance) → review+
(In reply to Ed Morley (Mostly away until 21st October) [:edmorley UTC+1] from comment #5) > Created attachment 817811 [details] [diff] [review] > Update csv source to builddata.pub.build.m.o > > build.m.o is no more, the csv now resides at: > http://builddata.pub.build.mozilla.org/reports/buildfaster.csv.gz > > Once this is checked in, happy for me to push to prod on brasstacks? > Presuming I just pull the repo there? Oh, and I have no problem with you pushing to prod on brasstacks, though at this point I'm not sure if I'm the right one to ask. I'm still happy to review patches, but IMO someone more closely involved with build efficiency should be responsible for keeping things running (interested?).
[root@brasstacks1.dmz.scl3 ~]# su - webtools [webtools@brasstacks1.dmz.scl3 ~]$ cd ~/apps/gofaster_dashboard/ [webtools@brasstacks1.dmz.scl3 gofaster_dashboard]$ git status # On branch master # Untracked files: # (use "git add <file>..." to include in what will be committed) # # bin/unit2-2.6 # deploy.sh # lib64 # src/dashboard/server/nohup.out nothing added to commit but untracked files present (use "git add" to track) [webtools@brasstacks1.dmz.scl3 gofaster_dashboard]$ git pull remote: Counting objects: 7, done. remote: Compressing objects: 100% (1/1), done. remote: Total 4 (delta 3), reused 4 (delta 3) Unpacking objects: 100% (4/4), done. From git://github.com/mozilla/gofaster 8be50ce..1933afb master -> origin/master Updating 8be50ce..1933afb Fast-forward bin/fetch-and-process-builddata.sh | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) ... [webtools@brasstacks1.dmz.scl3 ~]$ ./apps/gofaster_dashboard/bin/fetch-and-process-builddata.sh --2013-10-16 16:59:55-- http://builddata.pub.build.mozilla.org/reports/buildfaster.csv.gz Resolving builddata.pub.build.mozilla.org... 63.245.215.57 Connecting to builddata.pub.build.mozilla.org|63.245.215.57|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2162713 (2.1M) [text/plain] Saving to: â?oSTDOUTâ?? 100%[================================================>] 2,162,713 10.0M/s in 0.2s 2013-10-16 16:59:55 (10.0 MB/s) - written to stdout [2162713/2162713] -> http://brasstacks.mozilla.com/gofaster/#/executiontime/build now looks up to date :-) (Filed bug 927664 for the files not tracked in the repo).
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Oh and the data is imported once a day, at midnight PDT: [root@brasstacks1.dmz.scl3 gofaster_dashboard]# crontab -l -u webtools 0 0 * * * /home/webtools/apps/gofaster_dashboard/bin/fetch-and-process-builddata.sh ...
(In reply to William Lachance (:wlach) from comment #7) > Oh, and I have no problem with you pushing to prod on brasstacks, though at > this point I'm not sure if I'm the right one to ask. I'm still happy to > review patches, but IMO someone more closely involved with build efficiency > should be responsible for keeping things running (interested?). Possibly... ;-)
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: