Failing CI due to import path
See original GitHub issueDescription of issue or feature request:
After merging my pr https://github.com/theupdateframework/tuf/pull/1216 @jku noticed that one of the latest CI builds
https://travis-ci.com/github/theupdateframework/tuf/jobs/449593878
is failing.
The reason it seems that Travis CI is importing the wrong test package - the one from securesystemlib
instead of the one from TUF.
Current behavior:
Wrong import.
Expected behavior:
Import the tuf test package and the utils
module in it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Import module from above folder does not work with CI server
I have a working unit test python script under the folder "testing". In the unit python script I have sys.path.append("..") and then I...
Read more >Import of path failed modulePath #1531 - revel/revel - GitHub
Following instruction, have this error on the run: GOVERSION=go1.16 revel run my-app Revel executing: run a Revel application Downloading ...
Read more >Troubleshooting CI/CD - GitLab Docs
A new pipeline starts running on the example branch again, however, the previous pipeline (2) fails because of fatal: reference is not a...
Read more >How to Use a Private Go Module in Your Own Project
To tell Go that some import paths are private and that it shouldn't try to use the central Go services, you can use...
Read more >Usage and Invocations — pytest documentation
It defaults to fE to list failures and errors. Example: # content of test_example.py import pytest @pytest.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This further ties us to running tests from within the tests directory. But it seems like a reasonable quick fix.
For me the better fix is to not install securesystemslib as editable. I would welcome a patch for that @MVrachev