My feeling is that this problem is probably fixed in a newer Bazel version, so it could be automatically solved if we can package Bazel 5 or 6, but of course, that's not trivial work.
On Tue, Feb 21, 2023 at 4:04 PM Olek Wojnar <o...@debian.org> wrote: > Hi hc, > > Thanks for helping to start the conversation! > > > On February 21, 2023 2:38:14 PM UTC, Hans-Christoph Steiner <h...@at.or.at> > wrote: > > > >If the test passes regularly, and just sometimes fails under the same > conditions, I would consider disabling it in autopkgtest rather than have > it not make it into bookworm. The perfect is the enemy of the good. > > Unfortunately, the test fails pretty regularly now. This behavior started > when we moved to OpenJDK17. That makes sense since 'UseParallelOldGC' was > valid prior to that. > > I *have* temporarily disabled the Java tests [1]. As you said, to not hold > back the package due to a possibly flaky test. But my concern is that this > is actually an issue with how Bazel uses Java rather than a flaky test. > Again, I'd be happy to be wrong about that. :) > > -Olek > > [1] > https://salsa.debian.org/bazel-team/bazel-bootstrap/-/commit/1c90621d7b9b5d44d01b91dabb04645a20273ca8 > > -- > Mailing list: https://launchpad.net/~bazel-team > Post to : bazel-t...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~bazel-team > More help : https://help.launchpad.net/ListHelp >