Skip to content

Output From Failed subprocess.run Calls Not Captured #6445

Closed
@ericspod

Description

@ericspod

Describe the bug
In a few places such as here subprocess.run is called without any checks that a non-zero result was returned. In these situations the stdout/stderr from the call is lost and so doesn't appear in the output logs when CI/CD tests are run. It's difficult to reproduce the environment the test is run under so having this output is important for debugging when PR tests fail.

The solution is to use subprocess.run with capture_output=True and stderr=subprocess.STDOUT so that the raise exception will have that information. The exception should perhaps be caught and the output value it stores printed to stderr before being reraised. Other places where run or Popen are used might need modification as well.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions