SeaMonkey 2.26a1 has stopped being built on Linux x86_64

VERIFIED FIXED

Status

--
major
VERIFIED FIXED
5 years ago
5 years ago

People

(Reporter: tonymec, Assigned: ewong)

Tracking

Trunk
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26a1 ID:20140107003001 c-c:0c8f6b80f939 m-c:ce917d3dd7c8

The above is the latest SeaMonkey 2.26a1 nightly for Linux x86_64. No hourlies either AFAICT. All 3 other platforms (W32, L32 and Mac) are still being built.

This is not bug 943740 which started much earlier and did not prevent builds from 3 to 7 January on all *four* platforms.

AFAICT, 2.25a2 Aurora was never built for either L32 or L64 (it is being built for both W32 and Mac) but that is not this bug.
FWIW: the latest logs are .txt.gz files in subdirectories (which are not soft links) of ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-central-trunk-linux64/ — sort by mod time latest-first and they'll be the subdirectories named 1* at the top of the list.
Looks like a known error: wrong Python version

Creating Python environment
Python 2.7.3 or greater (but not Python 3) is required to build. You are running Python 2.6.5.
Run |mach bootstrap| to ensure your system is up to date.

If you still receive this error, your shell environment is likely detecting
another Python version. Ensure a modern Python can be found in the paths
defined by the $PATH environment variable and try again.
*** Fix above errors and then restart with               "make -f client.mk build"
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/builds/slave/c-cen-t-lnx64/build'
make: *** [objdir/Makefile] Error 2
program finished with exit code 2
elapsedTime=0.458057
Did we downgrade Python on the linux64 box again? Also see Bug 919126 Comment 5 on this.
(Assignee)

Comment 4

5 years ago
(In reply to Frank Wein [:mcsmurf] from comment #3)
> Did we downgrade Python on the linux64 box again? Also see Bug 919126
> Comment 5 on this.

Human error on my part.  Our configs were manually editted so I left out
linux64's path.  IN order to avoid this, I've reverted the manual stuff
and pushed a patch for bug 919126 which should fix the builds.
Assignee: nobody → ewong
Status: NEW → ASSIGNED
(Assignee)

Comment 5

5 years ago
(In reply to Frank Wein [:mcsmurf] from comment #3)
> Did we downgrade Python on the linux64 box again? Also see Bug 919126
> Comment 5 on this.

Incidentally this will regress our unittests back to bug 908090.  I've
submitted a patch for review.
(Assignee)

Updated

5 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26a1 ID:20140110130040 c-c:f444666b101c m-c:e89afc241513

is the hourly I'm running now.
You need to log in before you can comment on or make changes to this bug.