-
Notifications
You must be signed in to change notification settings - Fork 81
add align, chain, and net workflow #818
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
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Is there a non-GPU flag we can use in testing ? Otherwise I'm afraid we'll have to run the GPU step elsewhere, but I worry that's going to be a pain. |
@mvdbeek I am not sure if there is some non-gpu hack, I'll have a closer look. The test runs fine against vgp.usegalaxy.org but that is likely not very helpful here. edit: no hack found |
I think we'll have to invent some way to say that a workflow needs to run against a live instance when it really can't run in CI. Or perhaps the better way is to setup a "only for IWC" gpu pulsar destination. Then we only launch the step that needs special stuff against the remote resource. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Test Results (powered by Planemo)Test Summary
Errored Tests
|
FOR CONTRIBUTOR:
FOR REVIEWERS:
This workflow does/runs/performs … xyz … to generate/analyze/etc …
name
field should be human readable (spaces are fine, no underscore, dash only where spelling dictates it), no abbreviation unless generally understood-
) over underscore (_
), prefer all lowercase. Folder becomes repository in iwc-workflows organization and is included in TRS id