Somewhere, somehow, pawn (the tinderbox) got his name changed in the build graphs. He's now known as "pawn.local". This has bad affects on the build graphs as we lose all history when viewing them. So, to fix this, we need to merge the build graphs and rename the "pawn.local" tinderbox back to "pawn". This needs to be coordinated with email@example.com. The following steps should be followed, per rhelmer: <@rhelmer> 1) shut down tbox on pawn <@rhelmer> 2) merge graph <@rhelmer> 3) fix pawn's hostname <@rhelmer> 4) start up tbox on pawn
When did pawn become a he? I don't really know why the hostname changed from pawn to pawn.local, we can set it back by running "hostname" but we should probably just reboot pawn to make sure that it comes back up with the right name. If we set HOSTNAME=pawn in /etc/hostconfig, we'll probably have a better chance of it sticking.
Build has access to do the needed changes on the build graph server - assigning to them for the work.
Assignee: server-ops → build
Component: Server Operations → Build & Release
QA Contact: justin → preed
Gah. pawn decided to change _her_ name automatically. The second part of the bug summary has been fixed as a result (updating the summary as such). Now we just need to merge the build graph data from pawn.local back to pawn.office.mozilla.org. Is this a simpler process now? One we can get done quicker?
Summary: Merge pawn/pawn.local build graphs; rename pawn.local tinderbox → Merge pawn/pawn.local build graphs
WONTFIXing; this graph data is probably old-to-useless and pawn was supposed to go away as of April 2004.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX
Given the number of serious perf regressions on the trunk in mid-late 2006, many of which were Cocoa-only (or otherwise affect Camino more significantly), I would respectfully disagree that this data is "old-to-useless." It's our only graphic record of that perf.
The graphs are not gone, though, correct? They're just in two different places. You can still get the data you need by looking at both? And you can also get the csv's from build-graphs.m.o, right? If it's a historical representation you're after, someone should be able to munge those together.
(In reply to comment #6) > And you can also get the csv's from build-graphs.m.o, right? I wasn't aware of that, no, but getting the raw data and being able to then graph/etc. specific ranges myself would certainly be more useful. I've discovered rawdata.cgi; is there something that outputs actual CSVs, or is it simply create-your-own from that?
I think it's create-your-own from that.
Assignee: build → nobody
QA Contact: mozpreed → build
Status: RESOLVED → VERIFIED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.