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
[BEAM-3713] Move PerformanceTest and CrossLanguageValidateRunner from nosetest to pytest #14795
Conversation
Run XVR_Dataflow PostCommit |
Run XVR_Dataflow PostCommit |
What is the next step on this PR? |
Hi @aaltay! |
Run XVR_Dataflow PostCommit |
1 similar comment
Run XVR_Dataflow PostCommit |
R: @udim, Hi Udi, would you help me to review this?
|
"test_opts": config.pytestOptions, | ||
"suite": "xlangValidateRunner", | ||
"pytest": true, // TODO(BEAM-3713): Remove this once nose is removed. | ||
// TODO(BEAM-10507): Remove no_xlang_transforms after fixing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can remove this TODO. We will always want to exclude tests marked with no_xlang_transforms
.
@@ -36,7 +36,7 @@ | |||
PARQUET_WRITE_URN = "beam:transforms:xlang:test:parquet_write" | |||
|
|||
|
|||
@attr('UsesCrossLanguageTransforms') | |||
@pytest.mark.xlang_transforms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, you could remove the no_xlang_transforms
marker and just comment out this line with the same TODO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did this, I removed the no_xlang_transforms
marker and commented out those tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A successful run with changes in marker no_xlang_transforms
https://ci-beam.apache.org/job/beam_PostCommit_XVR_Dataflow_PR/23/testReport/
Run BigQueryIO Read Performance Test Python |
The run of |
Run Python37 WordCountIT Performance Test |
https://ci-beam.apache.org/job/beam_PerformanceTests_WordCountIT_Py37/2959/console failed. I think the pytest timeout of 600s might be the issue |
I think the same, I increased the timeout |
Run XVR_Dataflow PostCommit |
Hi @udim, would you help me to retest the wordcountIT performance test? |
Run Python37 WordCountIT Performance Test |
1 similar comment
Run Python37 WordCountIT Performance Test |
run was successful: https://ci-beam.apache.org/job/beam_PerformanceTests_WordCountIT_Py37/3002/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just needs to resolve the temporary TODO(BEAM-3713)s
Thanks, Udi, I removed the TODOs. |
Run Java PreCommit |
run python precommit |
Ignoring the precommit failures that seem unrelated |
Seems like this broke portable xvr tests. For example, ModuleNotFoundError: No module named 'pytest' (Flink and Spark test suites are broken as well) |
Fix in #15058 |
This change might have started to cause test flakiness: https://issues.apache.org/jira/browse/BEAM-12515 |
I don't see how this PR would affect how PipelineOptionsTest.test_display_data runs. It was running with pytest before this PR. |
I don't think this PR is related to that flakiness, I was able to reproduce it locally in code before this PR was merge using this plugin https://github.com/dropbox/pytest-flakefinder as: |
Possible fix for test_display_data flakiness in #15104 |
Move integration tests from nose to pytest on the following jobs:
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner
compliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.