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
try to fix CI problem #3142
try to fix CI problem #3142
Conversation
seems one test is looking for test data in the wrong place. obspy is installed with pip as editable, so in the Python tree there is only a link and setuptools plugin system still points us to that path that only has the link for plugin folders?
@trichter not sure if there was a reason for doing an editable install in CI, but it started to cause issues and it looks like a regular install does just fine.. |
I think for no specific reason. |
What I do not understand is, why this error appeared all of a sudden in the CI setup. I myself use this setup for my obspy installation. Will report when/if it breaks. |
I use editable installs all the time too, locally. But CI can have some special setups makin it weird, looks like auto stripping of test file directries maybe? Who knows.. |
I actually can reproduce the problem locally now.. happens when using a pip editable install and then going via |
For my local installation it is still working. Maybe a change in the entry points stuff of setuptools. Should we revert this PR? |
The underlying problem was fixed by #3175. On a fresh installation with all the newest packages and installing obspy editable after reverting that commit, it fails. As you say, seems to be a change in setuptools, reporting the shimmy directory instead of the git repository location as install base dir. Anyway, I dont care, if you want to revert this go ahead. EDIT: |
to reproduce:
|
Oh boy.. too many swapping around tabs and issues.. @trichter yes this change in CI script can be changed back to editable install if you want |
It's OK. I don't care enough. |
What does this PR do?
Changes obspy installation in CI from editable to a regular pip installation.
Also remove the
[tests]
modifier, which does nothing in combination with--no-deps
anyway and we rely on an environment file for all (testing) dependencies anyway.Why was it initiated? Any relevant Issues?
Some test currently fails because files are being looked up in the install location, which is only holding a link to the source tree though, due to being a pip editable installation.
obspy/obspy/core/tests/test_waveform_plugins.py
Lines 211 to 220 in 9d10a93
PR Checklist
master
for new features,maintenance_...
for bug fixesJust add the "build_docs" tag to this PR.
Docs will be served at docs.obspy.org/pr/{branch_name} (do not use master branch).
Please post a link to the relevant piece of documentation.
clients.fdsn
) should be tested for the PR,just add the "test_network" tag to this PR.
CHANGELOG.txt
.CONTRIBUTORS.txt
.from all the CI builds look correct. Add the "upload_plots" tag so that plotting
outputs are attached as artifacts.