Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Yun Peng Newsgroups: linux.debian.maint.java Subject: Re: [Bazel-team] Bazel Removal from Debian Date: Tue, 21 Feb 2023 16:30:01 +0100 Message-ID: References: X-Original-To: Olek Wojnar X-Mailbox-Line: From debian-java-request@lists.debian.org Tue Feb 21 15:27:13 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.701 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .google. - helo: .mail-vs1-xe29.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AO0yUKWYwLXmIwIbr9MbJXIpyYF0m3YaCkODls8+OOifPueIaqPOudK4 A4qsG0rW1q2gSs/6hDtUkXehLI5c8w5Rh7GiHMUKFg== X-Google-SMTP-Source: AK7set8Ano9tuDnIUMOTDUYNDXrwJM1iCQuJ5NMt1bMGrsxE2gIADyvxOyRMMW3wi8bZjg7s/Ax7fol+kRXbE/Wrlj8= X-Received: by 2002:a67:e454:0:b0:415:e432:da06 with SMTP id n20-20020a67e454000000b00415e432da06mr838538vsm.17.1676992304256; Tue, 21 Feb 2023 07:11:44 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000009678f505f53732c0" X-Mailing-List: archive/latest/23225 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAOZBPs4T3XE=Ka4QT4d8pkqks85sSmFBHnPE+QSb6_UZ2McvfA@mail.gmail.com Approved: robomod@news.nic.it Lines: 100 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Hans-Christoph Steiner , Debian Bazel Discussion List , Debian Java Discussion List , Debian Bazel Packaging Team X-Original-Date: Tue, 21 Feb 2023 16:11:33 +0100 X-Original-Message-ID: X-Original-References: <2FA11FED-1D3B-49A9-BA6E-F77AB13E0C62@debian.org> Xref: csiph.com linux.debian.maint.java:12570 --0000000000009678f505f53732c0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM Olek Wojnar wrote= : > Hi hc, > > Thanks for helping to start the conversation! > > > On February 21, 2023 2:38:14 PM UTC, Hans-Christoph Steiner > 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 hol= d > back the package due to a possibly flaky test. But my concern is that thi= s > 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/1c90621d7b9b= 5d44d01b91dabb04645a20273ca8 > > -- > Mailing list: https://launchpad.net/~bazel-team > Post to : bazel-team@lists.launchpad.net > Unsubscribe : https://launchpad.net/~bazel-team > More help : https://help.launchpad.net/ListHelp > --0000000000009678f505f53732c0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My feeling is that this problem is probably fixed in = a newer Bazel version, so it could be automatically solved if we can packag= e Bazel 5 or 6, but of course, that's not trivial work.

On Tue, Feb 21, = 2023 at 4:04=E2=80=AFPM Olek Wojnar <= olek@debian.org> wrote:
Hi hc,

Thanks for helping to start the conversation!


On February 21, 2023 2:38:14 PM UTC, Hans-Christoph Steiner <hans@at.or.at> wrote:
>
>If the test passes regularly, and just sometimes fails under the same c= onditions, I would consider disabling it in autopkgtest rather than have it= not make it into bookworm.=C2=A0 The perfect is the enemy of the good.

Unfortunately, the test fails pretty regularly now. This behavior started w= hen 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. Aga= in, I'd be happy to be wrong about that. :)

-Olek

[1] https://salsa.debian.org/bazel-team/bazel-bootstrap/-/commit/1c90621d7= b9b5d44d01b91dabb04645a20273ca8

--
Mailing list: https://launchpad.net/~bazel-team
Post to=C2=A0 =C2=A0 =C2=A0: bazel-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~bazel-team
More help=C2=A0 =C2=A0: https://help.launchpad.net/ListHelp
--0000000000009678f505f53732c0--