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] Moving integration tests from nose to pytest #14481
Conversation
Run Python 3.7 PostCommit |
Run Python Dataflow ValidatesContainer |
Run Python Dataflow ValidatesRunner |
R: @udim, could you take a look at this? Thanks in advance! |
Run Python 3.7 PostCommit |
Run PythonDocs PreCommit |
In https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont_PR/176/console I see this:
I see that you updated the |
rnu seed job |
run seed job |
Thanks Udi, I think the "Seed Job" is not triggering on the comment (https://ci-beam.apache.org/job/beam_SeedJob/), I was thinking maybe because I'm not a committer and that job probably only runs on committer's PRs. |
I believe this is true. And @tvalentyn had a work around for this. Maybe he could share, @udim could help with running tests. |
Running a seed job from a copy of this PR: https://ci-beam.apache.org/job/beam_SeedJob/7972/ (#14629) |
Run Python 3.7 PostCommit |
Run Python Dataflow ValidatesContainer |
https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont_PR/182/ passed and has test results correctly reported. Overall an improvement since it now has stderr/out captured. https://ci-beam.apache.org/job/beam_PostCommit_Python37_PR/257/ timed out after 1h40m. I think the above result is enough to verify the .groovy changes. |
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.
Some comments and lint failures, but otherwise LGTM
@attr('IT', 'ValidatesRunner', 'sickbay-batch') | ||
@pytest.mark.no_sickbay_batch | ||
@pytest.mark.it_validatesrunner | ||
@pytest.mark.it_postcommit |
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.
This is the only test that runs in both ValidatesRunner and post-commit. I think that's a bug but let's leave it for this PR.
Lint failure:
You can run lint checks locally as well using |
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.
Thanks!
Thanks to you |
Is it possible this broke Python PostCommits? They've been failing since this went in: https://ci-beam.apache.org/job/beam_PostCommit_Python38/1146/ |
…che#14481)" This reverts commit 38e879b
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.
Post-Commit 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.