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 < alessandro.solima...@gmail.com> 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 <jacq...@apache.org> 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 > > >
