Bugzilla

I started to hit this bug myself when I try to run TB's xpcshell-tests  (I use Debian. )
It took me a while to update my local patches to work with the recent directory layout change.

Funny, though, I could successfully run xpcshell-test of TB on June 16 and June 22.
I check mochitest more often and so didn't realize this bug has crept in.

What has changed?

my system python seems to be version 2 variety.
```
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ which python
/usr/bin/python
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ python --version
Python 2.7.18
```
whereas TB build process uses
```
 checking for Python 3... /NEW-SSD/moz-obj-dir/objdir-tb3/_virtualenvs/init_py3/bin/python (3.8.5)
```
But I just checked that python version 2 variety system binary is used for invoking xpcshell test locally.

Hmm. So maybe python2 vs python3 thingy as noted by some comments in the patch in 1622789/

Any idea when Ben's patch is installed soon?

TIA

I started to hit this bug myself when I try to run TB's xpcshell-tests  (I use Debian. )
It took me a while to update my local patches to work with the recent directory layout change.

Funny, though, I could successfully run xpcshell-test of TB on June 16 and June 22.
I check mochitest more often and so didn't realize this bug has crept in.

What has changed?

my system python seems to be version 2 variety.
```
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ which python
/usr/bin/python
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ python --version
Python 2.7.18
```
whereas TB build process uses
```
 checking for Python 3... /NEW-SSD/moz-obj-dir/objdir-tb3/_virtualenvs/init_py3/bin/python (3.8.5)
```
But I just checked that python version 2 variety system binary is used for invoking xpcshell test locally.

Hmm. So maybe python2 vs python3 thingy as noted by some comments in the patch in bug 1622789.

Any idea when Ben's patch is installed soon?

TIA