I now have a linux-debug machine set up for SeaMonkey, which performs the leak test steps defined in MercurialBuildFactory, and this works fine - except for one thing: It can't upload graph data anywhere. We need to figure out if/how that data can be uploaded to the Mozilla graph server, and eventually get an account set up there, or find a different solution to make those cycles go green - in the ideal case with having graphs up somewhere, of course. I was told on IRC that catlee and/or alice could possibly help there, is that right?
Summary: Graph data upload failing for SeaMonkey leak test buildbot → SeaMonkey buildbots fail graph data upload for leak/bloat/codesigs
Status: NEW → ASSIGNED
Component: Project Organization → Release Engineering
Product: SeaMonkey → mozilla.org
QA Contact: organization → release
Version: Trunk → other
Created attachment 376758 [details] [diff] [review] only post if graph server is set Here's the quite simple patch to buildbotcustom (already applied on my new master along with a config that explicitely sets None in config.py) so that we just don't post graphs if no graph server is set. I filed bug 492406 to hook us up to the graph server when the transition stuff is done.
Assignee: nobody → kairo
Attachment #376758 - Flags: review?(bhearsum)
Comment on attachment 376758 [details] [diff] [review] only post if graph server is set Looks good. I'll land this with the other patch tomorrow morning.
Attachment #376758 - Flags: review?(bhearsum) → review+
Comment on attachment 376758 [details] [diff] [review] only post if graph server is set changeset: 277:fc9a21be62e1
Attachment #376758 - Flags: checked‑in+
The new SeaMonkey buildbots are green with this fix and it's in generic buildbotcustom, so mark fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.