'ImportError: No module named argparse' on win32 comm-try build

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
3 months ago

People

(Reporter: clokep, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I just pushed to try [1] and saw this error:
> ImportError: No module named argparse
> mozbuild.frontend.reader.SandboxValidationError:
> mozmake.exe[2]: *** [configure] Error 1
> mozmake.exe[1]: *** [c:/builds/moz2_slave/tb-try-c-cen-w32-0000000000000/build/objdir-tb/Makefile] Error 2
> mozmake.exe: *** [build] Error 2 

Callek mentioned in #maildev that this had been seen earlier today and asked me to file a bug.

[1] https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=4ab82d3c4f64
(Reporter)

Updated

4 years ago
Flags: needinfo?(winter2718)
This problem is a result of our CentOS machines using Python 2.6 by default. I'm going through and trying to ensure that we explicitly run our utilities with 2.7, the problem should be fixed as of now.
Flags: needinfo?(winter2718)
(Reporter)

Comment 2

4 years ago
I retriggered the job and it seemed to compile OK this time. (Well it got past that part at least. :))

Thanks!
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 months ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.