Closed
Bug 741082
Opened 12 years ago
Closed 12 years ago
[sea-win32-02] "create aus previous upload dir failed"
Categories
(SeaMonkey :: Release Engineering, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.11
People
(Reporter: sgautherie, Assigned: Callek)
Details
(Keywords: regression)
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1333092636.1333099460.19366.gz&fulltext=1 WINNT 5.2 comm-central-trunk nightly on 2012/03/30 00:30:36 sea-win32-02 + http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1333092636.1333099460.19366.gz&fulltext=1 WINNT 5.2 comm-central-trunk nightly on 2012/03/30 00:30:36 sea-win32-02 { create aus previous upload dir failed ssh: connect to host aus2-community.mozilla.org port 22: Bad file number } Would that be related to the boxes moving from one location to another?
Assignee | ||
Comment 1•12 years ago
|
||
Taking so I can track this... (In reply to Serge Gautherie (:sgautherie) from comment #0) > Would that be related to the boxes moving from one location to another? Yes that is exactly it, the host cannot ssh into our aus2 from behind the new jumphost, needs network firewall flows opened up which may take some time, but should be able to happen this week. I'll get that bug on file, blocking this one, and turn off buildbot on sea-02 (to prevent this from hurting us more) tomorrow.
Assignee: nobody → bugspam.Callek
Reporter | ||
Updated•12 years ago
|
Blocks: 724968
Keywords: regression
Comment 2•12 years ago
|
||
I think this is fixed now? There's some cleanup remaining in bug 742571, but I believe these flows are fixed.
No longer blocks: 724968
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•12 years ago
|
||
This was not actually fixed....
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #3) > This was not actually fixed.... @Self, "huh it wasn't?" @Self, <rant> MORE INFORMATION WHEN YOU REOPEN BUGS. </rant> /me doesn't recall seeing an issue lately closing again.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•