-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test fail on appveyor after move to hatch #759
Comments
The reason for this is unclear, and requires a dedicated investigation. However, the general test setup is needed now, and this will have to wait for a moment. Refs: datalad#759
The reason for this is unclear, and requires a dedicated investigation. However, the general test setup is needed now, and this will have to wait for a moment. Refs: #759
The reason for this is unclear, and requires a dedicated investigation. However, the general test setup is needed now, and this will have to wait for a moment. Refs: #759
the ria failures are very very funky. I spent a while trying to make them fail on my local system. What ultimately did it was to set a pdb traceback in datalad: (datalad) adina@muninn in ~/repos/datalad on git:maint!
❱ git diff
diff --git a/datalad/customremotes/tests/test_ria_utils.py b/datalad/customremotes/tests/test_ria_utils.py
index 908512316..c58eb6228 100644
--- a/datalad/customremotes/tests/test_ria_utils.py
+++ b/datalad/customremotes/tests/test_ria_utils.py
@@ -121,7 +121,7 @@ def _test_setup_ds_in_store(io_cls, io_args, store=None):
def test_setup_ds_in_store():
-
+ import pdb; pdb.set_trace()
_test_setup_ds_in_store(LocalIO, [])
if on_windows: when I then run
When I then run the same command again, I get
and when I run the same command a third time, I get
and after running a fourth time I get
and the fifth run gives
absolutely no idea what is happening. Its probably worthwhile to note that the test suite doesn't end by itself but needs a CTRL-C after the summary (likely because of the breakpoint in datalad, although that breakpoint never brings me into a debugger during the test execution) |
I suspect that these tests are not cleanly implemented and suffer from and/or cause residuals in the environment that makes them order-dependent. This is, from my POV, the main change from the previous test setup to the new one. The tests run in random order now (each time). I think this is a good thing in and of itself. |
It smells like some kind of race condition, but I have no idea yet where it would come from...
test-linux
All these go away, when switching from PY3.9 Ubuntu 2204 to PY3.10 on Ubuntu2004, on a rerun
test_initremote_basic_sshurl
failure is back.test-linux-crippled
All these stay, when switching from PY3.9 Ubuntu 2204 to PY3.10 on Ubuntu2004. But on a rerun
test_version_check_ssh
works.test-win
All these stay, when switching from PY3.12 Win2022 to PY3.9 on Win2019. And stayed for a rerun.
test-mac
Only the last two stay when switching from PY3.12 sonoma to PY3.9 monterey. All came back after a rerun.
datalad-core-1
This is fragile and goes away on a rerun
datalad-core-4
All these went away, with no change on a rerun. And then came back on another rerun.
The text was updated successfully, but these errors were encountered: