-
Notifications
You must be signed in to change notification settings - Fork 85
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: check if extra files were created in Galaxy's file_path #1190
base: master
Are you sure you want to change the base?
test: check if extra files were created in Galaxy's file_path #1190
Conversation
3de0454
to
5a0fedd
Compare
question is why GALAXY_CONFIG_OVERRIDE_FILE_PATH is not set in the tests
It would be a nice alternative to configure Galaxy that executes the jobs in planemo such that jobs run as real user. Then jobs writing to the files dir would just fail. |
@bernt-matthias wouldn't it be easier to configure Galaxy a little bit. We are running already test with containers. We could now say that all inputs are just mounted in RO. We did something similar here: https://github.com/bgruening/galaxytools/blob/master/job_conf.xml_condor |
Thanks for sharing. Looks pretty simple. What was the original intention of using htcondor in CI? Is there somewhere an example for a param that sets up the a directory RO. I guess we can add this either to the planemo-ci-action .. or the separate repos, preferences? |
Is there a way to refer to the Galaxy root when specifying the paths? Do we actually need htcondor? Local docker might be sufficient as well. ... While reading the docs again wouldnt simply |
Hah. It does :) .. problem is that there might be tools that try to write and if impossible choose some different branch in the code. But as soon as the tools find a config that allows them to write then they will. So this PR might serve as a backup... Still the update_test_data should be implemented .. give me a sec :) |
This is an attempt to automatize galaxyproject/tools-iuc#3986 (comment)
fixes #1189
Seems difficult / impossible to find out which tool / test generates the extra files, so I just set all tests for failure and add some note to the stderr .. (but IUC style tests run 1
planemo test
per repo)I guess this will create quite a bit of noise in the IUC style repos weekly CI tests .. but maybe its a good thing.