You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am still trying to get up to speed on how build environments are setup, it looks like this error is a transient issue. Are python modules installed as part of each CI run, or is the host preconfigured to have python modules like this installed ahead of time via Ansible?
thanks for pointing that out @refack - it looks like i can reproduce this in a virtualenv on one of my FreeBSD systems:
(tap13) [pete@bells ~/tmp/tap13]$ bin/tap2junit --help
Traceback (most recent call last):
File "bin/tap2junit", line 6, in <module>
from tap2junit.__main__ import main
File "/usr/home/pete/tmp/tap13/lib/python3.6/site-packages/tap2junit/__main__.py", line 5, in <module>
from tap13 import TAP13 as tap13
ModuleNotFoundError: No module named 'tap13'
i created a fresh virtualenv, executed pip install tap2junit then tried to run the tap2junit script. hopefully i'll have some cycles to take a closer look today and see whats going on.
see also #1832
why is this happening now on multiple OSs? what's changed or is it just that we haven't been failing on this and haven't been properly parsing tap output on these machines?
I am willing to bet the machines that this still works on has python-2.7 installed and it is invoking the python-2.7 interpreter to execute.
I would suggest running it through "2to3-3.6" or something similar to see what will be needed to update to get this working. the code looks like it hasn't been touched since 2016, so it's not surprising it's not compatible: https://pypi.org/project/tap2junit/
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
Activity
sam-github commentedon Jun 8, 2019
@nodejs/platform-freebsd maybe?
nomadlogic commentedon Jun 8, 2019
I am still trying to get up to speed on how build environments are setup, it looks like this error is a transient issue. Are python modules installed as part of each CI run, or is the host preconfigured to have python modules like this installed ahead of time via Ansible?
I see subsequent builds do not have an issue with executing tap2junit, for example https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd11-x64/26740/console
(which seems to suffer from another issue).
refack commentedon Jun 8, 2019
@nomadlogic that's probably because we have two freebsd11 workers - https://ci.nodejs.org/label/freebsd11-x64/

The failing code comes from https://ci.nodejs.org/computer/test-digitalocean-freebsd11-x64-1
The job you refer to was run on https://ci.nodejs.org/computer/test-digitalocean-freebsd11-x64-2/
But the error is strange since
tap13.pyis there:And AFAICT
./should always be part of PYTHONPATH 😕nomadlogic commentedon Jun 8, 2019
thanks for pointing that out @refack - it looks like i can reproduce this in a virtualenv on one of my FreeBSD systems:
i created a fresh virtualenv, executed
pip install tap2junitthen tried to run the tap2junit script. hopefully i'll have some cycles to take a closer look today and see whats going on.refack commentedon Jun 8, 2019
Yeah I think I figured the issue. Default
pythonis 3.6, wheretap2junitapparently is only compatible with 2.7.refack commentedon Jun 8, 2019
P.S.
refack commentedon Jun 8, 2019
P.P.S. @nomadlogic if you still have the spare cycles and are comfortable with python, maybe you could figure out why this happens in 3.6?
nomadlogic commentedon Jun 8, 2019
heh i just realized this works with py27 on FreeBSD as well. I'll take a stab at seeing how to get this working py3.6.
rvagg commentedon Jun 11, 2019
see also #1832
why is this happening now on multiple OSs? what's changed or is it just that we haven't been failing on this and haven't been properly parsing tap output on these machines?
gem-pete commentedon Jun 11, 2019
I am willing to bet the machines that this still works on has python-2.7 installed and it is invoking the python-2.7 interpreter to execute.
I would suggest running it through "2to3-3.6" or something similar to see what will be needed to update to get this working. the code looks like it hasn't been touched since 2016, so it's not surprising it's not compatible:
https://pypi.org/project/tap2junit/
sam-github commentedon Aug 9, 2019
Related: #1847 (comment)
Trott commentedon Dec 14, 2019
tap2junit 0.1.5 is compatible with Python 3 and would seem to fix other bugs. Refs: nodejs/node#30955 (comment)
Can we update to tap2junit 0.1.5?
github-actions commentedon Oct 10, 2020
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.