If there is a systematic way to do it I would be interested to know. In the past, when I encountered similar hangs in CI what I ended-up doing is adding debugging commits in the PR with a thread printing stack traces of other threads at some intervals.
Best, Stamatis On Sun, Dec 12, 2021 at 7:00 PM Jacques Nadeau <[email protected]> wrote: > It could be infra but I'm wondering if it is some kind of concurrency bug. > > Anyone know if there is a straightforward way to add a secondary process in > a github workflow that takes a jstack after an hour or something (if the > tests run that long). Trying to jump on an instance when this happens and > do this manually sounds like an effort in frustration. > > I guess another option would be to modify the druid job to provide info on > tests that are running so that we can see if it always locks on the same > test. > > On Sat, Dec 11, 2021 at 11:39 PM Alessandro Solimando < > [email protected]> wrote: > > > I started noticing that intermittently around a month ago, I had a quick > > look back then but I could not pinpoint the root cause. > > > > I don't think it is expected, and I guess it comes from test infra setup > > rather than the Calcite code itself. > > > > Il Dom 12 Dic 2021, 05:43 Jacques Nadeau <[email protected]> ha > scritto: > > > > > I see a couple of recent builds with Druid tests hanging. Is that a > > normal > > > thing or something that has started recently. > > > > > > Examples: > > > > https://github.com/apache/calcite/runs/4487013505?check_suite_focus=true > > > > > > https://github.com/jacques-n/calcite/runs/4494836558?check_suite_focus=true > > > > > >
