-
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
Separate workflows for testing dandi dev between live and no network #435
Conversation
Log run: https://github.com/NeurodataWithoutBorders/nwbinspector/actions/runs/7904129986/job/21573692473 shows successful separation and passing tests on non-network DANDI tests |
on: workflow_call | ||
|
||
env: | ||
DANDI_TESTS_NONETWORK: "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's just me, but at first I always read as "none twork" 😅
DANDI_TESTS_NONETWORK: "1" | |
DANDI_TESTS_NO_NETWORK: "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I completely agree - this is the name of the environment variable that must be set to have this effect on the DANDI testing suite, so I cannot change it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah okay, thanks for the clarification!
Motivation
DANDI dev tests can sometimes fail due to live service issues like http://purl.obolibrary.org/ failing to respond (see dandi/dandi-cli#1405)
We should definitely still run all tests; but I'd prefer a separation so that when I get a notification of a failure, I can do a direct comparison between with network and without network, indicating that I should just wait a certain amount of time before rerunning the with network ones