Closed
Bug 613932
Opened 15 years ago
Closed 14 years ago
restarts pm01 and pm03 to fix PYTHONPATH
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Turns out that Buildbot doesn't like new entries to PYTHONPATH upon a reconfig. I had to hack around this this morning with some symlinks. Both of these masters need a restart after removing /tools/buildbotcustom/{release,build,util} from them. Their Makefiles are already updated to point to the real location of these modules.
Flags: needs-treeclosure?
Comment 1•14 years ago
|
||
I did a clean shutdown of pm03, removed /tools/buildbotcustom/{release,build,util}, and then started it back up.
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → bhearsum
Comment 2•14 years ago
|
||
Restarted pm01 too.
| Assignee | ||
Comment 3•14 years ago
|
||
We're done here, then.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•14 years ago
|
Flags: needs-treeclosure?
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•