[
https://issues.apache.org/jira/browse/BEAM-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460960#comment-17460960
]
Luke Cwik commented on BEAM-13456:
----------------------------------
Rerunning postcommit at prior commits to see if we can pinpoint the exact PR:
https://ci-beam.apache.org/job/beam_PostCommit_Java/8399/ - commit
414707077bb1f2689017d54076184c0b7d64955c
https://ci-beam.apache.org/job/beam_PostCommit_Java/8400/ - commit
e52bdf2add268cb0a9ce3b1fe405029a8e3da189
https://ci-beam.apache.org/job/beam_PostCommit_Java/8401/ - commit
06a5e67332aae53ea90dedb4ef6421c2a7d65035
https://ci-beam.apache.org/job/beam_PostCommit_Java/8402/ - last passing run at
b52762bf150cacceb0fdeb1f0dc85cbea6e6f39c
> beam_PostCommit_Java consistently timing out.
> ---------------------------------------------
>
> Key: BEAM-13456
> URL: https://issues.apache.org/jira/browse/BEAM-13456
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Affects Versions: 2.36.0
> Reporter: Daniel Oliveira
> Assignee: Luke Cwik
> Priority: P1
> Labels: currently-failing
> Attachments: 8jHFYMYydUhHrMe.png
>
>
> This seems to have first appeared with build #8367:
> [https://ci-beam.apache.org/job/beam_PostCommit_Java/8367/]
> Frustratingly, no build scans pop up when the test fails this way, and no
> error messages appear except for the timeout. It may be easiest to attempt to
> determine which commit introduced the error.
> The previous successful test is at commit
> b52762bf150cacceb0fdeb1f0dc85cbea6e6f39c
> The first failing test is at commit 06a5e67332aae53ea90dedb4ef6421c2a7d65035
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
