Closed
Bug 540144
Opened 14 years ago
Closed 14 years ago
MoMe Try Server has bug 537882 and bug 533418
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 533418
People
(Reporter: mcsmurf, Unassigned)
References
Details
When trying to create a SeaMonkey build on the MoMo try server, it fails during hg clone with this error: HTTPError: HTTP Error 404: Not Found abort: HTTP Error 404: Not Found Time: real 0.820 secs (user 0.010+0.000 sys 0.010+0.000) Traceback (most recent call last): File "client.py", line 428, in <module> do_hg_pull(os.path.join('mozilla', 'extensions', 'irc'), options.chatzilla_repo, options.hg, options.chatzilla_rev) File "client.py", line 232, in do_hg_pull check_call_noisy([hg, 'clone'] + hgopts + [repository, fulldir]) File "client.py", line 82, in check_call_noisy check_call(cmd, *args, **kwargs) File "/tools/python-2.5.1/lib/python2.5/subprocess.py", line 461, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['hg', 'clone', '--verbose', '--time', '--traceback', 'http://hg.mozilla.org/chatzilla/', './mozilla/extensions/irc']
Reporter | ||
Comment 1•14 years ago
|
||
Ping, anyone?
Comment 2•14 years ago
|
||
Sorry, the hg mirror used by the try server was missing chatzilla, and that got handled in some other bug I can't find at the moment. Can you try again? Should be working now.
Reporter | ||
Comment 3•14 years ago
|
||
Still seems to fail, see http://tinderbox.mozilla.org/showlog.cgi?log=ThunderbirdTry/1264513218.1264514222.5153.gz
Comment 4•14 years ago
|
||
Needed to reload configuration on the proxy server, done and verified working now.
Reporter | ||
Comment 5•14 years ago
|
||
Thanks, that seems to work, but now the Windows box breaks because of something different. Can I add it to this bug here? I'll open a new bug if yet another issue will appears ;-) I get this error in the build log: install --preserve-timestamps "/d/msvs8/VC/redist/x86/Microsoft.VC80.CRT"/Microsoft.VC80.CRT.manifest "/d/msvs8/VC/redist/x86/Microsoft.VC80.CRT"/msvcm80.dll "/d/msvs8/VC/redist/x86/Microsoft.VC80.CRT"/msvcp80.dll "/d/msvs8/VC/redist/x86/Microsoft.VC80.CRT"/msvcr80.dll ../../dist/bin This program sets up the installation of Vim 7.2 Inspecting system... ERROR: failed to rename vim.exe to vim.exx: No error The problem is Bug 506020, vim ships a install.exe. Workaround is either to rename this install.exe or change the path so that the d:\mozilla-build\vim\vim72 entry is behind the msys/mingw entries.
Comment 6•14 years ago
|
||
What solution is currently being used by SeaMonkey build boxes ? I'll just do the same.
Reporter | ||
Comment 7•14 years ago
|
||
Ben: Do you remember the solution/workaround for the install.exe vim problem that was used to fix this problem on the SeaMonkey Windows tinderboxen? Bug 506020 says to rename install.exe, but KaiRo told me some other workaround was used.
Comment 8•14 years ago
|
||
This bug is confusingly tracking two issues. Anywho, I don't think we did anything to work around this install.exe issue - it still exists in the vim72 folder on our slaves and is even the first 'install.exe' in PATH. Dunno what to tell you.
Reporter | ||
Comment 9•14 years ago
|
||
gozer: Can you rename the vim install.exe to something different then, for example vim-install.exe? KaiRo is quite sure something in the MozillaBuild installation was changed to prevent this from happening, but he does not know any details.
Comment 10•14 years ago
|
||
(In reply to comment #2) > handled in some other bug I can't find at the moment. That was bug 537882.
Depends on: 537882
Updated•14 years ago
|
Depends on: 506020
Summary: Try server SeaMonkey build fails due to 404 http error → MoMe Try Server has bug 537882 and bug 506020
Updated•14 years ago
|
Comment 11•14 years ago
|
||
Ok, this covers two issues, one is fixed (bug 537882) the other one appears to be bug 533418. Let's mark it as duplicate as it should have been already.
You need to log in
before you can comment on or make changes to this bug.
Description
•