Regression in 7.1 ? Windows CI started to fail with "assert mod not in mods" since 7.1 #9765

Carreau · 2022-03-14T10:33:31Z

Now sorry I know this is not a minimal reproducer, but I just want to log this here, and will investigate later:

You can see one Failure here

ERROR collecting test session 
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\runner.py:338: in from_call
    result: Optional[TResult] = func()
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\runner.py:369: in <lambda>
    call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\main.py:7[23](https://github.com/ipython/ipython/runs/5535021197?check_suite_focus=true#step:8:23): in collect
    for x in self._collectfile(pkginit):
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\main.py:575: in _collectfile
    ihook = self.gethookproxy(fspath)
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\main.py:539: in gethookproxy
    my_conftestmodules = pm._getconftestmodules(
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\config\__init__.py:579: in _getconftestmodules
    mod = self._importconftest(conftestpath, importmode, rootpath)
C:\hostedtoolcache\windows\Python\3.9.10\x64\lib\site-packages\_pytest\config\__init__.py:6[24](https://github.com/ipython/ipython/runs/5535021197?check_suite_focus=true#step:8:24): in _importconftest
    assert mod not in mods
E   AssertionError

Now I'm not sure what this does, but my quick understanding is that it checks whether conftest.py itself is not in the list of collected modules ? We might definitely do something wrong on IPython side, but it's strange as other non-windows CI are passing and regardless of whether this is something I did wrong, can the assert get an explanation messages as second argument ?

Downgrading to <7.1 fixes the issue.

Again I'll try to get a MVP/small example, but it may take me some time, and I guessed maybe one of you will immediately know why this is happening.

a detailed description of the bug or problem you are having
output of pip list from the virtual environment you are using
pytest and operating system versions
minimal example if possible

The text was updated successfully, but these errors were encountered:

bluetech · 2022-03-14T10:44:35Z

Thanks for the report, I will take a look when I get a chance. 7.1 had some internal conftest refactorings. If you manage to provide a reproduction that'd be great.

The-Compiler · 2022-03-14T10:57:13Z

One thing that seems somewhat suspicious is how IPython's pytest_ipdoctest.py seems to have some custom code around importing conftest files:

https://github.com/ipython/ipython/blob/d7cc335a36cdfe4159c9b88c94311866c923a547/IPython/testing/plugin/pytest_ipdoctest.py#L635-L646

Carreau · 2022-03-14T11:03:23Z

Yeah, it might be something on our end, we have to do some pretty weird things seeing we also an interpreter. So I would not be surprised if the problem is from our plugins.

Carreau · 2022-03-14T11:14:19Z

It does seem like removing the plugin fixes the issue,
I'm not quite sure why it's windows only, and I haven't written it, so I'm not sure how I can fix it.

Feel free to close, worse case I'll run the plugin only on linux CI.

See pytest-dev/pytest#9765

gonzalocasas · 2022-03-14T15:56:15Z

Not sure if it helps, I know it's not a slim repro setup, but this repo was just pinned to <7.1 because it was consistently reproducible in there: https://github.com/compas-dev/compas

- pytest-dev/pytest#9765 [skip ci]

bashtage · 2022-03-18T17:25:03Z

Seeing same in statsmodels on Windows.

https://dev.azure.com/statsmodels/statsmodels-testing/_build/results?buildId=4410&view=logs&j=9c2ba6b6-9ef1-5300-06cd-4db9cc34ebf3&t=f07685ef-4dee-5864-e861-bb3b9ab4fc6b

Carreau · 2022-03-18T17:46:13Z

@gonzalocasas and @bashtage I see both your CI install IPython in them, could you try pinning IPython to <8 to see if it's a problem with the IPython doctest plugin itself (that should not be present in 7.x)

bashtage · 2022-03-20T22:37:13Z

@Carreau I get the same error when I pip install ipython<8. I also get the same error when I pip uninstall ipython. Works find with 7.0.x, broken in 7.1.x.

bashtage · 2022-03-20T22:41:12Z

I can also get this error when I reun specific tests:

 ValueError: Plugin already registered: c:\git\statsmodels\statsmodels\conftest.py=<module 'statsmodels.conftest' from 'c:\\git\\statsmodels\\statsmodels\\conftest.py'>

jgb · 2022-04-08T08:38:19Z

I've got the same error, but on linux! Can't run any test on 7.1.x, reverting back to 7.0.x fixes the issue:

root@f786a0bfb51b:/srv/vidicenter# pytest -n4
WARNING No rollbar access token provided
Traceback (most recent call last):
  File "/usr/local/bin/pytest", line 8, in <module>
    sys.exit(console_main())
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 187, in console_main
    code = main()
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 145, in main
    config = _prepareconfig(args, plugins)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 324, in _prepareconfig
    config = pluginmanager.hook.pytest_cmdline_parse(
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_hooks.py", line 265, in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_manager.py", line 80, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_callers.py", line 55, in _multicall
    gen.send(outcome)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/helpconfig.py", line 102, in pytest_cmdline_parse
    config: Config = outcome.get_result()
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_result.py", line 60, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_callers.py", line 39, in _multicall
    res = hook_impl.function(*args)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 1016, in pytest_cmdline_parse
    self.parse(args)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 1304, in parse
    self._preparse(args, addopts=addopts)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 1206, in _preparse
    self.hook.pytest_load_initial_conftests(
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_hooks.py", line 265, in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_manager.py", line 80, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_callers.py", line 60, in _multicall
    return outcome.get_result()
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_result.py", line 60, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/usr/local/lib/python3.8/dist-packages/pluggy/_callers.py", line 39, in _multicall
    res = hook_impl.function(*args)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 1083, in pytest_load_initial_conftests
    self.pluginmanager._set_initial_conftests(
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 532, in _set_initial_conftests
    self._try_load_conftest(current, namespace.importmode, rootpath)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 551, in _try_load_conftest
    self._getconftestmodules(x, importmode, rootpath)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 575, in _getconftestmodules
    mod = self._importconftest(conftestpath, importmode, rootpath)
  File "/usr/local/lib/python3.8/dist-packages/_pytest/config/__init__.py", line 620, in _importconftest
    assert mod not in mods
AssertionError

bnavigator · 2022-04-26T12:31:07Z

FYI: I also get this in an rpmbuild of asdf for openSUSE Linux. I attribute it to some import mismatch for the conftest.py installed into the sitelib.

Fails:

Have asdf installed in sitelib but collect from asdf in source directory. This worked with pytest < 7

[    3s] Executing(%check): /usr/bin/bash -e /var/tmp/rpm-tmp.cC3tTE
[    3s] + umask 022
[    3s] + cd /home/abuild/rpmbuild/BUILD
[    3s] + cd asdf-2.11.1
[    3s] + export LANG=en_US.UTF-8
[    3s] + LANG=en_US.UTF-8
[    3s] + export PY_IGNORE_IMPORTMISMATCH=1
[    3s] + PY_IGNORE_IMPORTMISMATCH=1
[    3s] ++ '[' -f _current_flavor ']'
[    3s] ++ cat _current_flavor
[    3s] + last_flavor=python38
[    3s] + '[' -z python38 ']'
[    3s] + '[' python38 '!=' python39 ']'
[    3s] + '[' -d build ']'
[    3s] + mv build _build.python38
[    3s] + '[' -d _build.python39 ']'
[    3s] + mv _build.python39 build
[    3s] + echo python39
[    3s] + python_flavor=python39
[    3s] + PYTHONDONTWRITEBYTECODE=1
[    3s] + pytest-3.9 --ignore=_build.python39 --ignore=_build.python310 --ignore=_build.python38 -v --remote-data=none
[    3s] Internet access disabled
[    3s] ============================= test session starts ==============================
[    3s] platform linux -- Python 3.9.12, pytest-7.1.1, pluggy-1.0.0 -- /usr/bin/python3.9
[    3s] cachedir: .pytest_cache
[    3s] rootdir: /home/abuild/rpmbuild/BUILD/asdf-2.11.1, configfile: setup.cfg, testpaths: asdf, docs
[    3s] plugins: asdf-2.11.1, sugar-0.9.4, openfiles-0.5.0, doctestplus-0.12.0, remotedata-0.3.2
[    4s] collecting ... collected 0 items / 1 error
[    4s] 
[    4s] ==================================== ERRORS ====================================
[    4s] ________________________ ERROR collecting test session _________________________
[    4s] /usr/lib/python3.9/site-packages/_pytest/runner.py:338: in from_call
[    4s]     result: Optional[TResult] = func()
[    4s] /usr/lib/python3.9/site-packages/_pytest/runner.py:369: in <lambda>
[    4s]     call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
[    4s] /usr/lib/python3.9/site-packages/_pytest/main.py:723: in collect
[    4s]     for x in self._collectfile(pkginit):
[    4s] /usr/lib/python3.9/site-packages/_pytest/main.py:575: in _collectfile
[    4s]     ihook = self.gethookproxy(fspath)
[    4s] /usr/lib/python3.9/site-packages/_pytest/main.py:539: in gethookproxy
[    4s]     my_conftestmodules = pm._getconftestmodules(
[    4s] /usr/lib/python3.9/site-packages/_pytest/config/__init__.py:575: in _getconftestmodules
[    4s]     mod = self._importconftest(conftestpath, importmode, rootpath)
[    4s] /usr/lib/python3.9/site-packages/_pytest/config/__init__.py:620: in _importconftest
[    4s]     assert mod not in mods
[    4s] E   AssertionError
[    4s] =========================== short test summary info ============================
[    4s] ERROR  - AssertionError
[    4s] !!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
[    4s] =============================== 1 error in 0.29s ===============================
[    4s] error: Bad exit status from /var/tmp/rpm-tmp.cC3tTE (%check)

Works:

move the asdf source directory away and directly test with --pyargs asdf

[    3s] Executing(%check): /usr/bin/bash -e /var/tmp/rpm-tmp.wVMB1t
[    3s] + umask 022
[    3s] + cd /home/abuild/rpmbuild/BUILD
[    3s] + cd asdf-2.11.1
[    3s] + export LANG=en_US.UTF-8
[    3s] + LANG=en_US.UTF-8
[    3s] + mv asdf asdf.moved
[    3s] ++ '[' -f _current_flavor ']'
[    3s] ++ cat _current_flavor
[    3s] + last_flavor=python38
[    3s] + '[' -z python38 ']'
[    3s] + '[' python38 '!=' python39 ']'
[    3s] + '[' -d build ']'
[    3s] + mv build _build.python38
[    3s] + '[' -d _build.python39 ']'
[    3s] + mv _build.python39 build
[    3s] + echo python39
[    3s] + python_flavor=python39
[    3s] + PYTHONDONTWRITEBYTECODE=1
[    3s] + pytest-3.9 --ignore=_build.python39 --ignore=_build.python310 --ignore=_build.python38 -v --pyargs asdf --remote-data=none
[    3s] Internet access disabled
[    3s] ============================= test session starts ==============================
[    3s] platform linux -- Python 3.9.12, pytest-7.1.1, pluggy-1.0.0 -- /usr/bin/python3.9
[    3s] cachedir: .pytest_cache
[    3s] rootdir: /home/abuild/rpmbuild/BUILD/asdf-2.11.1, configfile: setup.cfg
[    3s] plugins: asdf-2.11.1, sugar-0.9.4, openfiles-0.5.0, doctestplus-0.12.0, remotedata-0.3.2
[    5s] collecting ... collected 721 items
[    5s] 
[    5s] asdf.py::asdf.asdf.AsdfFile.make_reference PASSED                        [  0%]
...
[  200s] ============ 691 passed, 8 skipped, 22 xfailed in 196.36s (0:03:16) ==========

chebee7i · 2022-05-11T21:16:18Z

Any chance this can be related to finding multiple conftest.py? This was working for us in linux on 7.0.1 and no longer working in 7.1.1. When we hackily removed conf files so that only one could be found, the issue went away.

So we've reverted and are pinning pytest to 7.0.1 for now.

Would be great to see this fixed, or provide a migration path for how to deal with it in 7.1.0. We are in a monorepo, and use the pytest runner for the entire repo (at the root). Has never been an issue in the past.

'assert mod not in mods' when run on Windows. See pytest-dev/pytest#9765

melund · 2022-07-04T08:42:38Z

Any chance this can be related to finding multiple conftest.py?

This could very well be the case. I had a colleague who had the same issue on Windows. It turned out to be triggered by him creating his the conda test environment as a subfolder inside the test folder (Not recommended)

So pytest was picking up an extra conftest.py file from the numpy folder in site-packages/ (numpy ships it tests files with the module)

jacksund · 2022-07-04T14:53:44Z

Just to add to this, the error occurs in my repo (issue 162) even when conda is set up properly (not as a subfolder like @melund describes). My repo only has a single conftest.py too. Leads me to believe this issue is happening in conda environments where installed dependencies also have conftest.py files. Maybe pytest is incorrectly grabbing conftest files from package dependencies. Is it that a possibility?

RonnyPfannschmidt · 2022-07-04T15:00:44Z

conftests are only ever searched locally, so unless you put evil magic in your tests folders you shouldnt see this

jacksund · 2022-07-04T15:11:28Z

lol good to know. I must have done some evil magic without realizing it 😅

tylerjereddy · 2024-01-07T00:05:25Z

@h-vetinari no, that's not right, the CI job that disables isolation is passing

tylerjereddy · 2024-01-07T01:50:17Z

I believe the wheels builds do disable build isolation though, because we pull in NumPy pre-release in anticipation of NumPy 2.0.0. Just not that specific CI job that uses Python 3.11 in our regular CI.

lesteve · 2024-01-07T05:28:11Z

@pllim can you try with (cherry-picked the commit but using the 0.8.x branch):

pip install git+https://github.com/lesteve/[email protected]

and post the output?

I guess @tylerjereddy you can do this as well?

lesteve · 2024-01-07T05:36:25Z

While we still don't have a proper reproduction for all cases, I believe we have a pretty good grasp of the issue and how to fix it (see #9765 (comment)).

I agree with this, thanks for looking into it and your very clear summary! I realised only now there was a question at the end of your summary post 😅. As far as I am concerned, 1. seems like the first straightforward thing to do. Without being super familiar with the pytest code, it is a bit hard to guess if 3. needs to be done but I feel this can be done in a second step.

Since @fcharras presumably hasn't had time to update PR #11708, I'll try to update it myself in the next few days so that we can backport it to pytest 8.0 release.

With @fcharras we'll try to work on this PR on Monday. I recently have worked on turning my reproducer into a pytest test so I think we should be close to having something mergeable.

pllim · 2024-01-07T17:02:29Z

@lesteve , thanks for the updated branch! I got a log but I don't understand how this error is related to "assert mod not in mods". I have not seen this error before as far as pytest 8.0rc is concerned.

https://github.com/spacetelescope/jdaviz/actions/runs/7439536734/job/20239554633?pr=2654

lesteve · 2024-01-08T08:08:30Z

@pllim not sure what is going on, ideally you would cherry-pick my simple debug commit on top of whichever version you were seeing the assert mod not in mods error before.

lesteve · 2024-01-08T10:49:41Z

@tylerjereddy looking closely at the Scipy CI logs, it could potentially be fixed by #11708, this is a os.path.normcase issue.

conftestpath has a capital L Lib, and mod.file has a small l lib. No idea why this would happen, and even less idea why only on Python 3.9 and Python 3.10 ...

Here is one relevant excerpt from your Python 3.10 log. You need to look at conftestpath vs mod.

  E   AssertionError
          conftestpath = WindowsPath('C:/Users/runneradmin/AppData/Local/Temp/cibw-run-flppgo17/cp310-win_amd64/venv-test/Lib/site-packages/scipy/conftest.py')
          dirpath    = WindowsPath('C:/Users/runneradmin/AppData/Local/Temp/cibw-run-flppgo17/cp310-win_amd64/venv-test/Lib/site-packages/scipy')
          existing   = None
          importmode = 'prepend'
          mod        = <module 'scipy.conftest' from 'C:\\Users\\runneradmin\\AppData\\Local\\Temp\\cibw-run-flppgo17\\cp310-win_amd64\\venv-test\\lib\\site-packages\\scipy\\conftest.py'>
          mods       = [<module 'scipy.conftest' from 'C:\\Users\\runneradmin\\AppData\\Local\\Temp\\cibw-run-flppgo17\\cp310-win_amd64\\venv-test\\lib\\site-packages\\scipy\\conftest.py'>]
          path       = WindowsPath('C:/Users/runneradmin/AppData/Local/Temp/cibw-run-flppgo17/cp310-win_amd64/venv-test/Lib/site-packages/scipy')
          pkgpath    = WindowsPath('C:/Users/runneradmin/AppData/Local/Temp/cibw-run-flppgo17/cp310-win_amd64/venv-test/Lib/site-packages/scipy')
          rootpath   = WindowsPath('C:/Users/runneradmin/AppData/Local/Temp/cibw-run-flppgo17/cp310-win_amd64/test_cwd')
          self       = <_pytest.config.PytestPluginManager object at 0x0000023B663B3D00>

pllim · 2024-01-08T16:40:41Z

@lesteve , I ended up forking 8.0rc1 on my fork and then cherry-pick your commit directly on top of that. I think this is the log you are requesting? Does this mean anything to you? Thanks! https://github.com/spacetelescope/jdaviz/actions/runs/7450389588/job/20269180187?pr=2654

lesteve · 2024-01-08T17:07:34Z

@pllim this seems very similar to the Scipy one, os.path.normcase issue, capital L Lib (in mod.__file__) vs small l lib (in conftestpath):

E   RuntimeError: mod=<module 'jdaviz.conftest' from 'D:\\a\\jdaviz\\jdaviz\\.tox\\py310-test-predeps\\lib\\site-packages\\jdaviz\\conftest.py'> has already been loaded
E   
E   str(conftestpath)='D:\\a\\jdaviz\\jdaviz\\.tox\\py310-test-predeps\\Lib\\site-packages\\jdaviz\\conftest.py'

I think this could be fixed by #11708. Hopefully we manage to push the PR forward tomorrow.

pllim · 2024-01-08T18:08:59Z

Thanks, @lesteve ! I will be happy to test that PR when it is ready.

lesteve · 2024-01-09T19:00:12Z

@pllim and maybe @h-vetinari or @tylerjereddy, can you try installing the code from #11708 and see whether that fixes your issue 🤞?

pip install git+https://github.com/fcharras/pytest@FIX/crash_during_conftest_collection

pllim · 2024-01-09T19:37:41Z

@lesteve , I applied the patch from fcharras to 8.0rc1 directly at https://github.com/pllim/pytest/tree/debug-8.0rc1 (pllim@22949f2). It went further this time but errored out because it cannot find test fixtures. We have a root level root/conftest.py and a root/package/conftest.py. The first one is so that tox picks up the pytest header stuff. The second one is where all the fixtures are and we need it at the package level so we can run package.test() command for any installed package (this uses the astropy test runner machinery).

Log: https://github.com/spacetelescope/jdaviz/actions/runs/7465954413/job/20316247352?pr=2654

For completeness, I can confirm that this problem only still happens on Windows. OSX passed and Linux failed with some transient remote data access problem that is unrelated to pytest itself.

lesteve · 2024-01-09T20:10:20Z

OK, so at least you avoid the assert mod not in mods and it goes a bit further, so I would count that as a win for the PR 😉 !

Your debug branch looks fine to me. Right now, I don't really understand how such a change could cause some fixtures to not be registered.

It could potentially be another pytest 8.0rc1 regression, hard to tell since I am by no means a pytest expert ...

pllim · 2024-01-09T20:18:34Z

Yes, I agree that the "assert mod not in mods" problem is solved in #11708

pllim · 2024-01-09T22:37:27Z

I also just found out that this "mod not in mods" problem on Windows is not a problem at all if I switch from Python 3.10 to Python 3.11 🤪 🤷‍♀️

Refs pytest-dev#9765. While this is probably not needed for fixing the `assert mod not in mods` bug (previous commit takes care of it), I believe this is the right thing to do to avoid other inconsistencies (see discussion in issue).

woutdenolf · 2024-01-14T20:00:36Z

For reference, in case this needs to be reproduced (Windows 11, python 3.8.10):

python -m pip install "ewokscore[test]==0.7.1" "pytest==8.0.0rc1"
python -m pytest -v --pyargs ewokscore.tests

This works fine (well there is an issue with the papermill dependency but that's not related to pytest)

python -m pip install "ewokscore[test]==0.7.1" "pytest==7.4.4"
python -m pytest -v --pyargs ewokscore.tests

lesteve · 2024-01-15T05:41:47Z

@woutdenolf this is similar to scipy and jdaviz see #9765 (comment), lib (small l) vs Lib (capital L).

I think this is fixed in main (since Saturday January 13 ~9PM Grenoble time) and in has been back-ported in the 8.0.x branch.

I double-checked and I don't get the assert mod not in mods on Windows and Python 3.8, when doing this:

python -m pip install "ewokscore[test]==0.7.1" git+https://github.com/pytest-dev/pytest.git@main
python -m pytest -v --pyargs ewokscore.tests

bluetech · 2024-01-15T21:31:12Z

For reference, the simple "Solution 3" normalize-as-early-as-possible approach (implemented here) does not work -- the problem is that, while Foo/Mod.py and foo/mod.py are equivalent paths in a case-insensitive filesystem, Foo.Mod and foo.mod are not equivalent Python module names.

woutdenolf · 2024-01-15T23:16:39Z

For reference, the simple "Solution 3" normalize-as-early-as-possible approach (implemented here) does not work -- the problem is that, while Foo/Mod.py and foo/mod.py are equivalent paths in a case-insensitive filesystem, Foo.Mod and foo.mod are not equivalent Python module names.

The link is broken. What do you mean by "normalize"? Normalize what and how?

I don't see the problem. You cannot import Foo/Mod.py by doing import foo.mod. Could you create an example?

I'm asking because I made a proposal that normalizes anymodule.__file__ but preserves symlinks: #11821. The tests pass so if there is a problem with this, it is not covered by the tests.

lesteve · 2024-01-16T05:26:37Z

The correct link for the commit is 203889b

Carreau mentioned this issue Mar 14, 2022

[Debugging pytest issue, please ignore] ipython/ipython#13593

Closed

gonzalocasas added a commit to compas-dev/compas that referenced this issue Mar 14, 2022

Avoid regression on pytest 7.1

960a97a

See pytest-dev/pytest#9765

Zac-HD added type: regression indicates a problem that was introduced in a release which was working previously topic: config related to config handling, argument parsing and config file labels Mar 15, 2022

WilliamJamieson mentioned this issue Mar 15, 2022

Update jsonschema to 4.x asdf-format/asdf#1105

Merged

eslavich mentioned this issue Mar 15, 2022

Pin pytest to < 7.1 for Windows asdf-format/asdf#1107

Merged

bkpoon added a commit to cctbx/cctbx that referenced this issue Mar 16, 2022

CI: use pytest<7.1 on Windows

53426aa

- pytest-dev/pytest#9765 [skip ci]

WilliamJamieson mentioned this issue Mar 17, 2022

Bugfixes for sphinx asdf-format/asdf#1111

Merged

TheBitShepherd mentioned this issue Mar 22, 2022

week 12 updates SFDO-Tooling/CumulusCI#3124

Merged

WilliamJamieson mentioned this issue Mar 24, 2022

Unpin pytest 7.1 for Windows asdf-format/asdf#1122

Closed

jacksund mentioned this issue Apr 29, 2022

Pytest v7.1 fails to initialize on windows jacksund/simmate#162

Closed

martinburchell added a commit to martinburchell/crate that referenced this issue May 26, 2022

Pin pytest to avoid assertion failure

3306409

'assert mod not in mods' when run on Windows. See pytest-dev/pytest#9765

Carreau mentioned this issue Aug 23, 2022

Rebuild for PyPy3.8 and PyPy3.9 conda-forge/ipython-feedstock#174

Closed

mattip mentioned this issue Aug 23, 2022

Build pytest<7 for pypy3.8/3.9 (and eventually python 3.11) conda-forge/pytest-feedstock#149

Closed

tylerjereddy mentioned this issue Jan 7, 2024

MAINT: follow-ups to gh-19724 (pytest pins, temporary CI changes, special ufunc type coercion) scipy/scipy#19826

Open

4 tasks

lesteve mentioned this issue Jan 8, 2024

Add test for Pytest issue 9765 fcharras/pytest#1

Merged

This comment was marked as outdated.

Sign in to view

lesteve mentioned this issue Jan 10, 2024

Improve assert mod not in mods error message #11795

Merged

takluyver mentioned this issue Jan 12, 2024

Temporarily pin pytest<8 for running tests h5py/h5py#2364

Merged

bluetech closed this as completed in #11708 Jan 13, 2024

woutdenolf mentioned this issue Jan 14, 2024

Main and 8.0.x (not released yet): cannot find fixture when using --pyargs #11816

Closed

4 tasks

This was referenced Jan 16, 2024

DO NOT MERGE: test Pytest main branch h5py/h5py#2367

Closed

MAINT: 1.12.x series tests still fail with pytest 8.0.0rc1 scipy/scipy#19847

Open

Uh oh!

Regression in 7.1 ? Windows CI started to fail with "assert mod not in mods" since 7.1 #9765

Regression in 7.1 ? Windows CI started to fail with "assert mod not in mods" since 7.1 #9765

Comments

Carreau commented Mar 14, 2022

bluetech commented Mar 14, 2022

Uh oh!

The-Compiler commented Mar 14, 2022

Uh oh!

Carreau commented Mar 14, 2022

Uh oh!

Carreau commented Mar 14, 2022

Uh oh!

gonzalocasas commented Mar 14, 2022

Uh oh!

bashtage commented Mar 18, 2022

Uh oh!

Carreau commented Mar 18, 2022

Uh oh!

bashtage commented Mar 20, 2022

Uh oh!

bashtage commented Mar 20, 2022

Uh oh!

jgb commented Apr 8, 2022

Uh oh!

bnavigator commented Apr 26, 2022

Fails:

Works:

Uh oh!

chebee7i commented May 11, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

melund commented Jul 4, 2022

Uh oh!

jacksund commented Jul 4, 2022

Uh oh!

RonnyPfannschmidt commented Jul 4, 2022

Uh oh!

jacksund commented Jul 4, 2022

Uh oh!

tylerjereddy commented Jan 7, 2024

Uh oh!

tylerjereddy commented Jan 7, 2024

Uh oh!

lesteve commented Jan 7, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lesteve commented Jan 7, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pllim commented Jan 7, 2024

Uh oh!

lesteve commented Jan 8, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lesteve commented Jan 8, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pllim commented Jan 8, 2024

Uh oh!

lesteve commented Jan 8, 2024

Uh oh!

pllim commented Jan 8, 2024

Uh oh!

lesteve commented Jan 9, 2024

Uh oh!

This comment was marked as outdated.

pllim commented Jan 9, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lesteve commented Jan 9, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pllim commented Jan 9, 2024

Uh oh!

pllim commented Jan 9, 2024

Uh oh!

woutdenolf commented Jan 14, 2024

Uh oh!

lesteve commented Jan 15, 2024

chebee7i commented May 11, 2022 •

edited

Loading

lesteve commented Jan 7, 2024 •

edited

Loading

lesteve commented Jan 7, 2024 •

edited

Loading

lesteve commented Jan 8, 2024 •

edited

Loading

lesteve commented Jan 8, 2024 •

edited

Loading

pllim commented Jan 9, 2024 •

edited

Loading

lesteve commented Jan 9, 2024 •

edited

Loading