Re: Buildbot failure in on tomcat-11.0.x
On Wed, Jun 12, 2024, 01:32 Mark Thomas wrote: > On 12/06/2024 01:46, Igal Sapir wrote: > > On Tue, Jun 11, 2024 at 5:32 PM wrote: > > > >> Build status: BUILD FAILED: failed Snapshot deployed to ASF Maven > snapshot > >> repository (failure) > >> Worker used: bb_worker2_ubuntu > >> URL: https://ci2.apache.org/#builders/112/builds/1130 > >> Blamelist: Igal Sapir > >> Build Text: failed Snapshot deployed to ASF Maven snapshot repository > >> (failure) > >> Status Detected: new failure > >> Build Source Stamp: [branch main] > 7118991902b3ae27e3ef128e86f94ef8b5dbb509 > >> > > > > I updated build.xml and .idea/tomcat.iml but I tested it locally and > there > > are no errors building Tomcat nor running the ide-intellij ant target. > The > > error message indicates an issue on the remote server from what I can > see: > > > > > /home/buildslave/slave/tomcat-11.0.x/build/res/maven/mvn-pub.xml:115: > > Could not deploy artifacts: Failed to deploy artifacts: Could not > transfer > > artifact > > > org.apache.tomcat:tomcat-annotations-api:pom:11.0.0-M21-20240612.002956-46 > > from/to apache.snapshots.https ( > > https://repository.apache.org/content/repositories/snapshots): status > code: > > 502, reason phrase: Proxy Error (502) > > > > I am not sure how to rerun the pipeline other than pushing another > commit. > After checking with the Infra people I realized that I have to login to Buildbot with the full ASF email address rather than just the username. > This happens from time to time. Once I see it is an issue with the Maven > repo I normally ignore it. > Got it, thanks! Igal > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Buildbot failure in on tomcat-11.0.x
On 12/06/2024 01:46, Igal Sapir wrote: On Tue, Jun 11, 2024 at 5:32 PM wrote: Build status: BUILD FAILED: failed Snapshot deployed to ASF Maven snapshot repository (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/1130 Blamelist: Igal Sapir Build Text: failed Snapshot deployed to ASF Maven snapshot repository (failure) Status Detected: new failure Build Source Stamp: [branch main] 7118991902b3ae27e3ef128e86f94ef8b5dbb509 I updated build.xml and .idea/tomcat.iml but I tested it locally and there are no errors building Tomcat nor running the ide-intellij ant target. The error message indicates an issue on the remote server from what I can see: /home/buildslave/slave/tomcat-11.0.x/build/res/maven/mvn-pub.xml:115: Could not deploy artifacts: Failed to deploy artifacts: Could not transfer artifact org.apache.tomcat:tomcat-annotations-api:pom:11.0.0-M21-20240612.002956-46 from/to apache.snapshots.https ( https://repository.apache.org/content/repositories/snapshots): status code: 502, reason phrase: Proxy Error (502) I am not sure how to rerun the pipeline other than pushing another commit. This happens from time to time. Once I see it is an issue with the Maven repo I normally ignore it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On Tue, Jun 11, 2024 at 5:32 PM wrote: > Build status: BUILD FAILED: failed Snapshot deployed to ASF Maven snapshot > repository (failure) > Worker used: bb_worker2_ubuntu > URL: https://ci2.apache.org/#builders/112/builds/1130 > Blamelist: Igal Sapir > Build Text: failed Snapshot deployed to ASF Maven snapshot repository > (failure) > Status Detected: new failure > Build Source Stamp: [branch main] 7118991902b3ae27e3ef128e86f94ef8b5dbb509 > I updated build.xml and .idea/tomcat.iml but I tested it locally and there are no errors building Tomcat nor running the ide-intellij ant target. The error message indicates an issue on the remote server from what I can see: /home/buildslave/slave/tomcat-11.0.x/build/res/maven/mvn-pub.xml:115: Could not deploy artifacts: Failed to deploy artifacts: Could not transfer artifact org.apache.tomcat:tomcat-annotations-api:pom:11.0.0-M21-20240612.002956-46 from/to apache.snapshots.https ( https://repository.apache.org/content/repositories/snapshots): status code: 502, reason phrase: Proxy Error (502) I am not sure how to rerun the pipeline other than pushing another commit. Igal > > > Steps: > > worker_preparation: 0 > > git: 0 > > shell: 0 > > shell_1: 0 > > shell_2: 0 > > shell_3: 0 > > shell_4: 0 > > shell_5: 0 > > shell_6: 0 > > compile: 1 > > shell_7: 0 > > shell_8: 0 > > shell_9: 2 > > > -- ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Buildbot failure in on tomcat-11.0.x
This is my fault. The fix for BZ 68119 is bad. I have the corrections locally. I'm just double checking everything. Mark On 27/11/2023 15:06, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/766 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 79a0e29a611d582135ebfb3740c060363c13f877 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 shell_6: 0 compile: 1 shell_7: 0 shell_8: 0 shell_9: 0 shell_10: 0 Rsync docs to nightlies.apache.org: 0 shell_11: 0 Rsync RAT to nightlies.apache.org: 0 compile_1: 2 shell_12: 0 Rsync Logs to nightlies.apache.org: 0 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On 24/10/2023 22:13, Rémy Maucherat wrote: It's running on Java 22 now, there's a red warning at the top in the -release-java-check target otherwise. The check can be flipped back to fail if there's no Java 22 when trying a release (because the build would be incomplete). The OpenSSL tests with FFM are running but are all failing because OpenSSL is not loadable. I don't quite understand why right now since the regular OpenSSL tests are working. Looks like an issue with java.library.path I'm looking at it now... Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On Tue, Oct 24, 2023 at 10:00 PM Mark Thomas wrote: > > On 24/10/2023 12:34, Mark Thomas wrote: > > On 24/10/2023 10:04, Rémy Maucherat wrote: > >> On Tue, Oct 24, 2023 at 10:51 AM Mark Thomas wrote: > >>> > >>> This was triggered by the switch to Java 22. > >>> > >>> I'm going to need to update the CI. The Tomcat 11 builds are going to > >>> fail until I get that done. > >> > >> That was not intended, I simply forgot this CI was using the release > >> target (the github one does not, it uses deploy). Disabling the check > >> for now is easier until CI can reasonably have Java 22 available. > >> Sorry for the trouble ... > > > > No problem. I've filed INFRA-25120 to make the Java 22 EA 20 available > > on the buildbot nodes. Once it is, I'll update the CI build and report > > back. > > Buildbot should updated to use Java 22. What should I look for in the > next build to check it is working as expected? It's running on Java 22 now, there's a red warning at the top in the -release-java-check target otherwise. The check can be flipped back to fail if there's no Java 22 when trying a release (because the build would be incomplete). The OpenSSL tests with FFM are running but are all failing because OpenSSL is not loadable. I don't quite understand why right now since the regular OpenSSL tests are working. Rémy > Mark > > > > > > I'll also switch Gump to Java 22. > > > > Mark > > > >> > >> Rémy > >> > >>> Mark > >>> > >>> > >>> On 24/10/2023 09:45, build...@apache.org wrote: > Build status: BUILD FAILED: failed compile (failure) > Worker used: bb_worker2_ubuntu > URL: https://ci2.apache.org/#builders/112/builds/701 > Blamelist: remm > Build Text: failed compile (failure) > Status Detected: new failure > Build Source Stamp: [branch main] > ee1f16a323d5e07b59f0de7a3b17cb495896f3e7 > > > Steps: > > worker_preparation: 0 > > git: 0 > > shell: 0 > > shell_1: 0 > > shell_2: 0 > > shell_3: 0 > > shell_4: 0 > > shell_5: 0 > > compile: 2 > > > -- ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >>> For additional commands, e-mail: dev-h...@tomcat.apache.org > >>> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: dev-h...@tomcat.apache.org > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On 24/10/2023 12:34, Mark Thomas wrote: On 24/10/2023 10:04, Rémy Maucherat wrote: On Tue, Oct 24, 2023 at 10:51 AM Mark Thomas wrote: This was triggered by the switch to Java 22. I'm going to need to update the CI. The Tomcat 11 builds are going to fail until I get that done. That was not intended, I simply forgot this CI was using the release target (the github one does not, it uses deploy). Disabling the check for now is easier until CI can reasonably have Java 22 available. Sorry for the trouble ... No problem. I've filed INFRA-25120 to make the Java 22 EA 20 available on the buildbot nodes. Once it is, I'll update the CI build and report back. Buildbot should updated to use Java 22. What should I look for in the next build to check it is working as expected? Mark I'll also switch Gump to Java 22. Mark Rémy Mark On 24/10/2023 09:45, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/701 Blamelist: remm Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] ee1f16a323d5e07b59f0de7a3b17cb495896f3e7 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 2 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On 24/10/2023 10:04, Rémy Maucherat wrote: On Tue, Oct 24, 2023 at 10:51 AM Mark Thomas wrote: This was triggered by the switch to Java 22. I'm going to need to update the CI. The Tomcat 11 builds are going to fail until I get that done. That was not intended, I simply forgot this CI was using the release target (the github one does not, it uses deploy). Disabling the check for now is easier until CI can reasonably have Java 22 available. Sorry for the trouble ... No problem. I've filed INFRA-25120 to make the Java 22 EA 20 available on the buildbot nodes. Once it is, I'll update the CI build and report back. I'll also switch Gump to Java 22. Mark Rémy Mark On 24/10/2023 09:45, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/701 Blamelist: remm Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] ee1f16a323d5e07b59f0de7a3b17cb495896f3e7 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 2 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On Tue, Oct 24, 2023 at 10:51 AM Mark Thomas wrote: > > This was triggered by the switch to Java 22. > > I'm going to need to update the CI. The Tomcat 11 builds are going to > fail until I get that done. That was not intended, I simply forgot this CI was using the release target (the github one does not, it uses deploy). Disabling the check for now is easier until CI can reasonably have Java 22 available. Sorry for the trouble ... Rémy > Mark > > > On 24/10/2023 09:45, build...@apache.org wrote: > > Build status: BUILD FAILED: failed compile (failure) > > Worker used: bb_worker2_ubuntu > > URL: https://ci2.apache.org/#builders/112/builds/701 > > Blamelist: remm > > Build Text: failed compile (failure) > > Status Detected: new failure > > Build Source Stamp: [branch main] ee1f16a323d5e07b59f0de7a3b17cb495896f3e7 > > > > > > Steps: > > > >worker_preparation: 0 > > > >git: 0 > > > >shell: 0 > > > >shell_1: 0 > > > >shell_2: 0 > > > >shell_3: 0 > > > >shell_4: 0 > > > >shell_5: 0 > > > >compile: 2 > > > > > > -- ASF Buildbot > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
This was triggered by the switch to Java 22. I'm going to need to update the CI. The Tomcat 11 builds are going to fail until I get that done. Mark On 24/10/2023 09:45, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/701 Blamelist: remm Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] ee1f16a323d5e07b59f0de7a3b17cb495896f3e7 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 2 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
6 Oct 2023 08:41:59 Rémy Maucherat : On Fri, Oct 6, 2023 at 12:50 PM wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/659 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 4c4dac3ee551c73afd173f50d3c8653cd2a496f9 The translation for versionLoggerListener.vm.vendor in catalina.startup for RU is causing problems. Not sure why. I'll delete the string in poeditor. Also there is an extra EOL space at the end of some other RU strings that were added that makes checkstyle unhappy. Thanks for fixing this. I'll look into fixing this in the import process. Mark Rémy Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 1 shell_6: 0 shell_7: 0 shell_8: 0 shell_9: 0 Rsync docs to nightlies.apache.org: 0 shell_10: 0 Rsync RAT to nightlies.apache.org: 0 compile_1: 2 shell_11: 0 Rsync Logs to nightlies.apache.org: 0 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On Fri, Oct 6, 2023 at 12:50 PM wrote: > > Build status: BUILD FAILED: failed compile (failure) > Worker used: bb_worker2_ubuntu > URL: https://ci2.apache.org/#builders/112/builds/659 > Blamelist: Mark Thomas > Build Text: failed compile (failure) > Status Detected: new failure > Build Source Stamp: [branch main] 4c4dac3ee551c73afd173f50d3c8653cd2a496f9 The translation for versionLoggerListener.vm.vendor in catalina.startup for RU is causing problems. Not sure why. I'll delete the string in poeditor. Also there is an extra EOL space at the end of some other RU strings that were added that makes checkstyle unhappy. Rémy > > > Steps: > > worker_preparation: 0 > > git: 0 > > shell: 0 > > shell_1: 0 > > shell_2: 0 > > shell_3: 0 > > shell_4: 0 > > shell_5: 0 > > compile: 1 > > shell_6: 0 > > shell_7: 0 > > shell_8: 0 > > shell_9: 0 > > Rsync docs to nightlies.apache.org: 0 > > shell_10: 0 > > Rsync RAT to nightlies.apache.org: 0 > > compile_1: 2 > > shell_11: 0 > > Rsync Logs to nightlies.apache.org: 0 > > > -- ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
This is my fault. I know what I did wrong - I missed one case in the fix for BZ 66841. Working on a fix now... Mark On 04/08/2023 16:51, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/513 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 5972c56e562a04cce558530cd4c3659f0d36eaef Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 1 shell_6: 0 shell_7: 0 shell_8: 0 shell_9: 0 Rsync docs to nightlies.apache.org: 0 shell_10: 0 Rsync RAT to nightlies.apache.org: 0 compile_1: 2 shell_11: 0 Rsync Logs to nightlies.apache.org: 0 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
This was an APR crash on shutdown. I've see a couple of these recently but haven't spotted a pattern. Nor have they bee frequent enough to be repeatable. Mark On 27/07/2023 17:11, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/496 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] ca06a33bd42af8f0d384802b61be83cbfd48ccc2 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 1 shell_6: 0 shell_7: 0 shell_8: 0 shell_9: 0 Rsync docs to nightlies.apache.org: 0 shell_10: 0 Rsync RAT to nightlies.apache.org: 0 compile_1: 2 shell_11: 0 Rsync Logs to nightlies.apache.org: 0 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
Sorry about this. I thought I ran the tests locally before committing the redirect changes but obviously not. Trying to figure out the root cause of the failure now... Mark On 14/03/2023 15:04, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/255 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 6c841c949b8b6a36a4318a3cbe21c2d345007a66 Steps: worker_preparation: 0 git: 0 shell: 0 shell_1: 0 shell_2: 0 shell_3: 0 shell_4: 0 shell_5: 0 compile: 1 shell_6: 0 shell_7: 0 shell_8: 0 shell_9: 0 Rsync docs to nightlies.apache.org: 0 shell_10: 0 Rsync RAT to nightlies.apache.org: 0 compile_1: 2 shell_11: 0 Rsync Logs to nightlies.apache.org: 0 -- ASF Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On 12/01/2023 22:16, Mark Thomas wrote: On 12/01/2023 20:01, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb2_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/115 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 65392b14e87e585289990b0dd65af87f58ab8c3f This is related to the multicast deprecation changes. The tests pass on Java 17 but fail on Java 11. I'm investigating... Oh that is just pure genius. The behaviour of IP_MULTICAST_LOOP is inverted for Java 14+. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8234643 I cannot believe that this change has not be back-ported to Java 11 and Java 8. Well actually, I can. I suspect it wasn't back-ported due to fear of breakage. This looks like a job for JreCompat. Sigh. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Buildbot failure in on tomcat-11.0.x
On 12/01/2023 20:01, build...@apache.org wrote: Build status: BUILD FAILED: failed compile (failure) Worker used: bb2_worker2_ubuntu URL: https://ci2.apache.org/#builders/112/builds/115 Blamelist: Mark Thomas Build Text: failed compile (failure) Status Detected: new failure Build Source Stamp: [branch main] 65392b14e87e585289990b0dd65af87f58ab8c3f This is related to the multicast deprecation changes. The tests pass on Java 17 but fail on Java 11. I'm investigating... Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
