AnandInguva opened a new issue, #29022: URL: https://github.com/apache/beam/issues/29022
### What happened? Pip was updated to 23.3 and there are some failures observed in the Python test suites in GitHub actions. If multiple virtual environments are installing the same package at the same time one of them can/will fail with a cache error similar to the one below. For example, https://github.com/apache/beam/actions/runs/6538469207/job/17754466856?pr=29016 and https://github.com/apache/beam/actions/runs/6538469213/job/17754476104?pr=29016  Related issued I found on `pypa/pip`: https://github.com/pypa/pip/issues/12361. ### Issue Failure Failure: Test is flaky ### Issue Priority Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy) ### Issue Components - [X] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
