Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Hans-Christoph Steiner Newsgroups: linux.debian.maint.java Subject: Re: Bazel Removal from Debian Date: Tue, 21 Feb 2023 15:40:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Tue Feb 21 14:38:48 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.881 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=unavailable autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .at. - helo: .wout2-smtp.messagingengine. - helo-domain: .messagingengine.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Me-Sender: X-Me-Received: X-Me-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejjedgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffggfuvfevfhfhohgjtgfgsehtjeertddttdejnecuhfhrohhmpefjrghn shdqvehhrhhishhtohhphhcuufhtvghinhgvrhcuoehhrghnshesrghtrdhorhdrrghtqe enucggtffrrghtthgvrhhnpeetteffgeeigfetudekvdeujefglefhkedtjeetkeeuhfeu uddtudeuudehjefhhfenucffohhmrghinhepuggvsghirghnrdhorhhgnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephhgrnhhssegrthdrohhr rdgrth X-Me-Proxy: Feedback-ID: i264a41e9:Fastmail MIME-Version: 1.0 Content-Language: en-US Organization: @||@ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/23223 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/cd29859e-57c2-6326-0472-5044e736499c@at.or.at Approved: robomod@news.nic.it Lines: 32 Sender: robomod@news.nic.it X-Original-Cc: Debian Bazel Packaging Team X-Original-Date: Tue, 21 Feb 2023 15:38:14 +0100 X-Original-Message-ID: X-Original-References: <2FA11FED-1D3B-49A9-BA6E-F77AB13E0C62@debian.org> Xref: csiph.com linux.debian.maint.java:12569 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. .hc Olek Wojnar: > Fellow Bazel contributors (and Java Team members), > > I've discussed this with a few of you but I want this to go to the widest possible audience right now. We still have no idea why Bazel Java tests are failing [1] and it seems to indicate an actual problem with Bazel, as opposed to just a flaky test. (It would be nice if I'm wrong about that) To save people a click, the failing error is: > Unrecognized VM option 'UseParallelOldGC' > (Which has been patched out of the code [2] so I have no idea where it's coming from) > > So, if we cannot fix this, I'll have to remove Bazel from Debian testing before the bookworm release. Meaning Bazel will NOT be in the next stable Debian release. > > 1 March 2023 is the last day to make an upload that will definitely make it in before the Hard Freeze. > > So, I'm asking all interested people to please please take a look and see if you can figure out how to fix either the tests or the suspected underlying issue. > > Pull Requests from your own branch in the bazel-bootstrap repository [3] are preferred but I'll take patches or even "you should look at line xxx in this one source file." > > Please reply to this thread with any ideas or suggestions. Hopefully with all our eyes on this we can make this really frustrating bug a bit more shallow. > > Thanks in advance!! > > -Olek > > [1] https://salsa.debian.org/bazel-team/bazel-bootstrap/-/jobs/3862692 > [2] https://salsa.debian.org/bazel-team/bazel-bootstrap/-/blob/master/debian/patches/fix_JDK-16_test_failures.patch > [3] https://salsa.debian.org/bazel-team/bazel-bootstrap >