[
https://issues.apache.org/jira/browse/BEAM-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347181#comment-17347181
]
Kyle Weaver commented on BEAM-12258:
------------------------------------
Thanks for clarifying, Brian. I'm curious how you found the earlier failure?
Not even knowing which class is stuck is painful. The simplest solution may be
to just slap a very high (10-20min) per-test Junit timeout on the dozen-or-so
test classes in this suite. Unfortunately, it looks like Gradle doesn't have
builtin support for this, so the alternative is to install a plugin. I looked
up [https://github.com/tableau/gradle-test-timeout] but it isn't published, so
we'd have to copy and build it ourselves.
> SQL postcommit timing out
> -------------------------
>
> Key: BEAM-12258
> URL: https://issues.apache.org/jira/browse/BEAM-12258
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql, test-failures
> Reporter: Kyle Weaver
> Assignee: Brian Hulette
> Priority: P1
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> SQL postcommit ([https://ci-beam.apache.org/job/beam_PostCommit_SQL/)] is
> timing out (and the timeout is already 4 hours!). Looks like it's stuck on
> "Task :sdks:java:extensions:sql:integrationTest".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
