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
This is not our bug, but I'm opening it to track the interaction here.
I think it might already be filed upstream as this — tox-dev/tox#2844 but the symptom is hard to nail down exactly. From ps/pgrep/pstree output it looks like the test process in the environment is never started, but the console shows it as if it's running forever. I left one overnight to make sure it wasn't a zealous timeout.
I switched back to tox 3 for my local use, and thankfully none of the tox.ini changes we made to upgrade seem to have negatively affected old versions, so I'm going to stick with that. It doesn't seem to have any issues in CI, so perhaps the bug is macOS specific?
The text was updated successfully, but these errors were encountered:
Mainly I wanted to open this to ensure that we don't start depending on any tox 4 features and make this workaround impossible. Although maybe it's time to switch to nox
This is not our bug, but I'm opening it to track the interaction here.
I think it might already be filed upstream as this — tox-dev/tox#2844 but the symptom is hard to nail down exactly. From
ps
/pgrep
/pstree
output it looks like the test process in the environment is never started, but the console shows it as if it's running forever. I left one overnight to make sure it wasn't a zealous timeout.I switched back to tox 3 for my local use, and thankfully none of the
tox.ini
changes we made to upgrade seem to have negatively affected old versions, so I'm going to stick with that. It doesn't seem to have any issues in CI, so perhaps the bug is macOS specific?The text was updated successfully, but these errors were encountered: