-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[23.1] Fix tool remote test data #16311
[23.1] Fix tool remote test data #16311
Conversation
80422df
to
d484dab
Compare
Anything I can do to help? Maybe test? |
Sure! Testing would be ideal, or any other improvements too :) |
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.
I successfully tested the code with planemo (using the calisp tool from the proteomics tool repo where I already prepared for test data download).
@@ -87,7 +87,6 @@ | |||
<tool file="is_valid_xml.xml" /> | |||
<tool file="expression_tools/parse_values_from_file.xml"/> | |||
<tool file="expression_tools/pick_value.xml" /> | |||
<tool file="remote_test_data_location.xml" /> |
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.
Why not keep it?
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.
I guess it doesn't need to run as part of the framework functional tool tests anymore. Looks like It is being tested here though... https://app.circleci.com/pipelines/github/galaxyproject/galaxy/32282/workflows/a028ae07-de5c-40b6-9ff1-bb865729bdd4/jobs/193407?invite=true#step-105-413
But I'm happy to add it back if it makes sense, I'm just not sure where is the correct place for testing this.
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.
I guess this is only linting the tools (which is also important). Otherwise I would be wondering about the test runtime of 192.47 seconds :)
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.
Ahh true! lol
@mvdbeek any chance that we get this in 23.1? |
@bernt-matthias It's fine to get this in as a bugfix during the freeze. |
Should I retarget 23.1 as a "fix" then? or it would be enough just to publish a new version of the |
Let's do 23.1 then. It isn't really necessary since we can do dev releases, but I guess it's also nice not to require dev releases in non-dev planemo versions. |
This solution was suboptimal as it moved around too much unnecessary data
- Remove checksum support for inputs for now
Co-authored-by: M Bernt <m.bernt@ufz.de>
de68bfa
to
d8937d4
Compare
Thank you @mvdbeek! |
Follow up on #15510 and #16291
This PR reverts most of the changes in #15510 as that approach was moving too much unnecessary data back and forth to Galaxy.
The new implementation is simpler and makes use of the pasted URL upload for inputs. The only difference in functionality with the previous implementation is that there is no checksum verification for remote inputs for now as we are still using the
upload1
tool to upload test datasets (we can use the__DATA_FETCH__
that supports checksums to upload test data in future improvements).How to test the changes?
location
attributes (like test/functional/tools/remote_test_data_location.xml and there is no local test data already present.galaxy-tool-test
with the appropriate parameters to test your toolLicense