Skip to content
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

jobs.py: Fix subprocess.run() output capture #203

Merged
merged 1 commit into from
Mar 4, 2024

Conversation

tescande
Copy link
Contributor

@tescande tescande commented Mar 4, 2024

The 'capture_output' prameter for subprocess.run() has been introduced in python 3.7. Use 'stdout=subprocess.PIPE' and 'stderr=subprocess.PIPE' instead for our Jenkins server running python 3.6.

Also print more information about the host version under test.

@tescande tescande requested review from stormi and gduperrey March 4, 2024 08:34
@tescande tescande self-assigned this Mar 4, 2024
@tescande tescande marked this pull request as draft March 4, 2024 09:03
The 'capture_output' and 'text' parameters for subprocess.run() have
been introduced in python 3.7. This change uses 'stdout=subprocess.PIPE'
instead for our Jenkins server running python 3.6.

Also print more information about 'lsb_release' possible failure and the
host version under test.

Signed-off-by: Thierry Escande <[email protected]>
@tescande tescande force-pushed the fix/jobs.py_subprocess_output_capture branch from de67be8 to d998b6b Compare March 4, 2024 09:22
@tescande tescande marked this pull request as ready for review March 4, 2024 09:24
@tescande tescande merged commit 09c057e into master Mar 4, 2024
4 checks passed
@tescande tescande deleted the fix/jobs.py_subprocess_output_capture branch March 4, 2024 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants