Skip to content

Conversation

@MarcoRob
Copy link
Contributor

@MarcoRob MarcoRob commented Sep 15, 2022

As part of the migration of Precommit and Postcommit Jobs from Jenkins to GA in self-hosted runners, this PR contains:

The migrated workflows were added to CI.md

DO NOT MERGE until the effort to use self-hosted runners is completed #22703
These workflows use base actions listed in #23109 (Dependency)


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI.

@MarcoRob MarcoRob force-pushed the GABR-110-VR-flink-samza-twister branch from e954381 to 1cd3ab3 Compare September 28, 2022 15:29
@MarcoRob MarcoRob marked this pull request as ready for review October 3, 2022 17:18
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2022

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @Abacn for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @Abacn

@github-actions
Copy link
Contributor

github-actions bot commented Dec 1, 2022

Reminder, please take a look at this pr: @Abacn

fail-fast: false
matrix:
flink-versions: ${{fromJson(needs.set-properties.outputs.properties).JavaTestProperties.FLINK_VERSIONS}}
exclude: # exclude other versions, we only need 1.13 for this test
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should do the same thing as in the other test if we only need 1.13 (use that as the version instead of an exclude list)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recently bumped DataProc to 2.1 which runs flink 1.15. DataProc never supports flink 1.13 (Dataproc 2.0 runs flink 1.12)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Abacn should we just be pinning to 1.15 across both suites? Probably?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I would suggest. For Jenkins it is set here:

static String getFlinkVersion() {
we could also define a single test version for Github Action.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @damccorm
So for this workflow, should I use the 1.15 flink version instead of 1.13?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I can apply the change, just I tested using 1.15 but the test failed, I changed back to 1.13 and the test passed. 🤔

Copy link
Contributor

@damccorm damccorm Dec 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Abacn any ideas? https://github.com/MarcoRob/beam/actions/runs/3622938989/jobs/6108239170

I recently bumped DataProc to 2.1 which runs flink 1.15. DataProc never supports flink 1.13 (Dataproc 2.0 runs flink 1.12)

Does this actually affect this set of tests? Or are these just running on a local cluster? My guess is that its all local

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, that change does not affect local clusters. Running flink 1.13 on local cluster does not involve DataProc and does not have problem. For test failure not sure the cause, but we can defer the version aligning as future task if bumping version breaks test.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change applied using Flink Version 1.13, I applied the following property as FLINK_DEFAULT_VERSION

@codecov
Copy link

codecov bot commented Dec 2, 2022

Codecov Report

Merging #23267 (e1cd5c4) into master (8dea86b) will decrease coverage by 0.02%.
The diff coverage is n/a.

❗ Current head e1cd5c4 differs from pull request most recent head 52e377f. Consider uploading reports for the commit 52e377f to get more accurate results

@@            Coverage Diff             @@
##           master   #23267      +/-   ##
==========================================
- Coverage   73.40%   73.37%   -0.03%     
==========================================
  Files         718      719       +1     
  Lines       95652    97206    +1554     
==========================================
+ Hits        70211    71323    +1112     
- Misses      24130    24536     +406     
- Partials     1311     1347      +36     
Flag Coverage Δ
go 51.64% <ø> (+0.75%) ⬆️
python 82.98% <ø> (-0.18%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...python/apache_beam/examples/complete/distribopt.py 0.00% <0.00%> (-98.57%) ⬇️
...hon/apache_beam/examples/cookbook/mergecontacts.py 23.21% <0.00%> (-73.22%) ⬇️
...he_beam/examples/cookbook/multiple_output_pardo.py 37.50% <0.00%> (-58.34%) ⬇️
...python/apache_beam/examples/wordcount_debugging.py 38.77% <0.00%> (-57.15%) ⬇️
...python/apache_beam/examples/dataframe/wordcount.py 38.46% <0.00%> (-53.85%) ⬇️
...s/python/apache_beam/examples/wordcount_minimal.py 40.74% <0.00%> (-51.86%) ⬇️
sdks/python/apache_beam/examples/wordcount.py 48.27% <0.00%> (-44.83%) ⬇️
...apache_beam/examples/cookbook/custom_ptransform.py 53.65% <0.00%> (-41.58%) ⬇️
.../apache_beam/examples/cookbook/group_with_coder.py 51.16% <0.00%> (-34.89%) ⬇️
sdks/python/apache_beam/examples/complete/tfidf.py 73.43% <0.00%> (-24.95%) ⬇️
... and 159 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@github-actions
Copy link
Contributor

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 11, 2023
@pabloem
Copy link
Member

pabloem commented Feb 11, 2023

hmmm what should we do here @damccorm ?

@github-actions github-actions bot removed the stale label Feb 12, 2023
@damccorm
Copy link
Contributor

Lets leave this open for now so that we can take this effort forward if we're able to get the resources to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants