Closed
Bug 687208
Opened 13 years ago
Closed 13 years ago
Tree closure hook for Jaegermonkey
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhackett1024, Assigned: cshields)
Details
I get this while trying to push to JM. pushing to ssh://bhackett@mozilla.com@hg.mozilla.org/projects/jaegermonkey searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files remote: Unrecognized tree! I don't know how to check closed status for jaegermonkey. remote: transaction abort! remote: rollback completed remote: abort: pretxnchangegroup.a_treeclosure hook failed abort: unexpected response: empty string Why isn't the default to allow pushes on unrecognized trees? This is slowing me down.
Comment 1•13 years ago
|
||
I can't find any bugs asking for the hook to be added, there's no tree status html in http://tinderbox.mozilla.org/Jaegermonkey/status.html, and no jaegermonkey entry in http://hg.mozilla.org/hgcustom/hghooks/file/ebea31cf1cc0/mozhghooks/treeclosure.py#l23. --> Over to IT to remove the hook from hg.mozilla.org/projects/jaegermonkey
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
OS: Mac OS X → All
QA Contact: release → cshields
Comment 2•13 years ago
|
||
(In reply to Brian Hackett from comment #0) > Why isn't the default to allow pushes on unrecognized trees? This is > slowing me down. Interesting, it *used* to fail open on unrecognized trees. At least as far as I can recall. I know the comm* closure hook does fail-open.
Reporter | ||
Comment 3•13 years ago
|
||
Can someone fix this ASAP? This is blocking me from being able to push to JM.
Assignee | ||
Updated•13 years ago
|
Assignee: server-ops → cshields
Assignee | ||
Comment 4•13 years ago
|
||
This hook was added per bug 664493 I've removed the hooks from jaegermonkey. Please reopen if you still run into issues.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•