You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "tvalentyn (via GitHub)" <gi...@apache.org> on 2023/09/21 06:00:16 UTC
[GitHub] [beam] tvalentyn opened a new issue, #28578: [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all poscommit suite.
tvalentyn opened a new issue, #28578:
URL: https://github.com/apache/beam/issues/28578
### What would you like to happen?
Current test configuration causes confusion for authors of new suites and makes some test suites run twice (see discussions on: https://github.com/apache/beam/pull/28571 https://github.com/apache/beam/pull/28534)
### Issue Priority
Priority: 3 (nice-to-have improvement)
### Issue Components
- [X] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite. [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #28578:
URL: https://github.com/apache/beam/issues/28578#issuecomment-5046073529
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite. [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #28578: [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite.
URL: https://github.com/apache/beam/issues/28578
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite. [beam]
Posted by "damccorm (via GitHub)" <gi...@apache.org>.
damccorm commented on issue #28578:
URL: https://github.com/apache/beam/issues/28578#issuecomment-1783372534
I don't think this should be a release blocker. The problem in question is that tests are running more often than they should, which doesn't represent risk to users.
@tvalentyn I'm removing the release blocker, if you disagree feel free to add it back
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] AnandInguva commented on issue #28578: [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite.
Posted by "AnandInguva (via GitHub)" <gi...@apache.org>.
AnandInguva commented on issue #28578:
URL: https://github.com/apache/beam/issues/28578#issuecomment-1735796198
if a test is using `it_postcommit` along with a ML framework marker, it is considered to be an IT test. These IT tests then will be run on Dataflow with the respective requirements file. We provide both the markers because we want to only collect IT tests of that ML framework but not unit tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Rewrite pytest markers to avoid including ML test suites into a catch-all postcommit suite. [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #28578:
URL: https://github.com/apache/beam/issues/28578#issuecomment-5380491601
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org