Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAutomatically transfer task 'stdout' and 'stderr' #363
Comments
This comment has been minimized.
This comment has been minimized.
This issue depends on #219 |
This comment has been minimized.
This comment has been minimized.
Or support streaming of stdout/err. This would be useful for development/testing. E.g., Example from Francois:
|
This comment has been minimized.
This comment has been minimized.
The test suite contains at least one test for stdout/stderr which makes assumptions about std file appending/location: This test is likely to not work in the presence of any kind of non-shared filesystem, which this issue is related to. |
This comment has been minimized.
This comment has been minimized.
I think staging of these parameters should be made to be the same as for any other I put and output file, using a |
Tests which inspect stdout/stderr cannot always expect to find the stdout/stderr files on the submitting file system. That is issue #363 This commit adds @pytest.mark.issue363, so that pytest can be invoked with parameter: -k 'not issue363' which skips tests affected in that way. I have tested this with the AWS provider (as part of a set of various other AWS test fixes and local configs).
Tests which inspect stdout/stderr cannot always expect to find the stdout/stderr files on the submitting file system. That is issue #363 This commit adds @pytest.mark.issue363, so that pytest can be invoked with parameter: -k 'not issue363' which skips tests affected in that way. I have tested this with the AWS provider (as part of a set of various other AWS test fixes and local configs).
annawoodard commentedJul 1, 2018
We allow a user to pass
stdout
andstderr
keywords to bash apps, but these have no effect if the app is run remotely. We should automatically transfer these files back. Related to #276 and #361.