A1K28 opened a new pull request, #35830:
URL: https://github.com/apache/beam/pull/35830

   fixes #30813 
   
   This PR fixes multiple issues for the 
.github/workflows/beam_PreCommit_Python_Coverage.yml workflow runs (different 
runs exhibited different errors). One of which was more interesting than 
others. Specifically, some of the workflows failed because of the following 
error message: 
   
   ```bash
          TimeoutError: Wait time (1s) exceeded for _connect(args: (), kwargs: 
{}). Exception: Error while reading from localhost:32777 : (104, 'Connection 
reset by peer')
   ```
   Which is caused by a decorator function inside the testcontainers library 
that repeatedly waits for a redis server to come up. The default value of 
TC_MAX_TRIES should have been 120, however something modifies this and sets it 
to 1. I could not find the culprit in the the repository code, it's likely some 
framework that does this. However, the changes in this PR will overwrite 
TC_MAX_TRIES and set it to 30 for now.
   
   Additionally, after checking multiple past failing workflows, and since all 
these five issues were captured in different runs, there could be more issues 
that come up later on. but I suppose we'll fix them as they are uncovered.
   
   Successful run: 
https://github.com/A1K28/beam/actions/runs/16830044494/job/47675287136
   
   In conclusion, the tests are somewhat brittle, and this workflow will likely 
become flaky again in the near future, since more test failures may surface.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] 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](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](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](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to