-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Failing Test]: GHA Java_GCP_IO_Direct is failing consistently at "Publish JUnit Test Results" step #28803
Comments
This happens between https://github.com/apache/beam/actions/runs/6342568605/job/17228698749 - 2023-09-28 18:05 and https://github.com/apache/beam/actions/runs/6351240606/job/17252181160 - 2023-09-29 12:02 where there is timeout in two runs in between https://github.com/apache/beam/actions/runs/6345499725/job/17237578555 - 2023-09-29 00:06 |
I could not find a possible change on beam side; and EnricoMi/publish-unit-test-result-action does not have new release in that time period. From the log, the exception happens between publish - INFO - Finished reading 202 files in 0.52 seconds and publish - INFO - Publishing failure results for commit ... Persumably its failing connect to 'api.github.com'. This happens after moving this workflow to highmem: #28719 |
CC: @volatilemolotov |
#28804 reverted - keep the issue open to resolve the credential / connection issue on highmem cluster |
Note that the enroll of highmem runner for python postcommit is also reverted due to another error on highmem cluster:
|
https://github.com/apache/beam/actions/runs/6402157556 Its working on main now. Ill investigate what might be different with highmem group (usually nothing is, except machine type and requests) |
@Abacn https://github.com/apache/beam/actions/workflows/beam_PreCommit_Java_GCP_IO_Direct.yml test is now flaky but it is passing from time to time. Not sure what changes happened |
What happened?
Stack trace:
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
The text was updated successfully, but these errors were encountered: