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

Terminate test earlier if pytest ENV issue [skip ci] #5169

Merged
merged 2 commits into from
Apr 8, 2022

Conversation

pxLi
Copy link
Collaborator

@pxLi pxLi commented Apr 8, 2022

Signed-off-by: Peixin Li pxli@nyu.edu

We saw get cases/tests by tag funcs could hide errors in pipefails
Instead of deal w/ PIPESTATUS and adjust string manipulation, we simply add a pytest ENV check (~20s) before the actual test run which will also expose all stdout&stderr to console. e.g. SPARK ENV issue, cuda ENV issue, pytest dep issue, etc

also remove redundant 311 ver check since we support spark311+ only

tested internally.

@pxLi pxLi added the build Related to CI / CD or cleanly building label Apr 8, 2022
GaryShen2008
GaryShen2008 previously approved these changes Apr 8, 2022
@pxLi pxLi changed the base branch from branch-22.06 to branch-22.04 April 8, 2022 05:12
@pxLi pxLi dismissed GaryShen2008’s stale review April 8, 2022 05:12

The base branch was changed.

Signed-off-by: Peixin Li <pxli@nyu.edu>
@pxLi pxLi force-pushed the catch-pytest-collect-only-execption branch from 61902f5 to 5f90b3c Compare April 8, 2022 05:13
@pxLi
Copy link
Collaborator Author

pxLi commented Apr 8, 2022

build

@pxLi
Copy link
Collaborator Author

pxLi commented Apr 8, 2022

retargeted to 22.04

@pxLi
Copy link
Collaborator Author

pxLi commented Apr 8, 2022

build

@pxLi pxLi merged commit ed27a8c into NVIDIA:branch-22.04 Apr 8, 2022
@sameerz sameerz added this to the Apr 4 - Apr 15 milestone Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Related to CI / CD or cleanly building
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants