Closed Bug 395966 Opened 13 years ago Closed 13 years ago

make perfmaster buildmaster log properly and respond to reconfigs

Categories

(Release Engineering :: General, defect)

All
Linux
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

After running for a short period of time (a few days to a week) perfmaster stops logging and refuses to reconfig. The unit test buildmaster also exhibits this behaviour. I believe the culprit here is Twisted 2.5.0. The Try Server is running Twisted 2.4.0 and does not have this problem.

I am installing Python 2.5/Twisted 2.4.0 in /tools/python2.5.0-twisted2.4 and will be running a test Buildmaster until Monday. If there is heavy log activity (ie. log is rotated at least once) and it is still logging and responsive to reconfigs I will consider this confirmation that Twisted 2.5.0 is the culprit.
staging-perfmaster is running on Python2.5/Twisted 2.4 with qm-mini-xp01 as a slave. Now we wait...
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Blocks: 393044
Blocks: 395931
perfmaster is up and running on Python 2.5/Twisted 2.4. Marking FIXED, will reopen if necessary.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.