1373936 - mach wpt-manifest-update fails with: Exception: Error populating virtualenv.

Status: RESOLVED INVALID

(Firefox Build System :: MozillaBuild, task)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

MozillaBuild 3.0pre2

Running |mach wpt-manifest-update| fails with:

$ mach wpt-manifest-update
New python executable in c:\Mozilla\Coding\Code\autoland\obj-i686-pc-mingw32\_virtualenv\Scripts\python2.7.exe
Not overwriting existing python script c:\Mozilla\Coding\Code\autoland\obj-i686-pc-mingw32\_virtualenv\Scripts\python.exe (you must use c:\Mozilla\Coding\Code\autoland\obj-i686-pc-mingw32\_virtualenv\Scripts\python2.7.exe)
Installing setuptools, pip, wheel...done.
Error running mach:

    ['wpt-manifest-update']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.

You should consider filing a bug for this issue.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

Exception: Error populating virtualenv.

  File "c:\Mozilla\Coding\Code\autoland\testing/web-platform/mach_commands.py", line 433, in wpt_manifest_update
    self.setup()
  File "c:\Mozilla\Coding\Code\autoland\testing/web-platform/mach_commands.py", line 353, in setup
    self._activate_virtualenv()
  File "c:\Mozilla\Coding\Code\autoland\python/mozbuild\mozbuild\base.py", line 626, in _activate_virtualenv
    self.virtualenv_manager.ensure()
  File "c:\Mozilla\Coding\Code\autoland\python/mozbuild\mozbuild\virtualenv.py", line 166, in ensure
    return self.build(python)
  File "c:\Mozilla\Coding\Code\autoland\python/mozbuild\mozbuild\virtualenv.py", line 450, in build
    raise Exception('Error populating virtualenv.')

This works if I run it from MozillaBuild 2.2.0. Issue with 32- vs. 64-bit Python?

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Did you clobber after installing 3.0? You're definitely going to have a bad time if not due to the differences in Python. FWIW, I can't reproduce.

Comment 2

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Now that you say it... didn't clobber after updating fro 3.0pre1 to 3.0pre2. Clobber fixed it.

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Yay! Thanks for testing it, BTW!