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
Implement job and tool stdio separation #318
Conversation
hmm, 20 new test errors for the framework tests against the master branch (22.05). I guess that was to be expected, but it's no good that dev seem to time out on the parallelism tests |
7493cbe
to
fc5b791
Compare
Feel free to just increase that complexity threshold if it is a complex thing to "fix". |
3993072
to
19daf80
Compare
Alright, the directory metadata variant framework tests pass completely! And the extended metadata tests seem to just have an issue with the stdio redirection. |
19daf80
to
ab5a528
Compare
and always set up job i/o redirection on the pulsar side. Since pulsar stdio is broken prior to this on 23.0 this is maybe a good time to make the switch. Seems like this detail should be controlled on pulsar, not Galaxy.
This will write to metadata/memory_statement.log, instead of the working directory. Fixes a bunch of tests that use metadata collection.
ab5a528
to
a0ee452
Compare
7ce2875
to
ec37128
Compare
ec37128
to
1bab112
Compare
I've deployed this as https://pypi.org/project/pulsar-galaxy-lib/0.15.0.dev2/ for testing on the Galaxy side (galaxyproject/galaxy#15915) |
and always set up job i/o redirection on the pulsar side. Since pulsar stdio is broken prior to this on 23.0 this is maybe a good time to make the switch. Seems like this detail should be controlled on pulsar, not Galaxy.