I suggest the following: - Refactor the failing test methods into a new test class. - Document the environmental requirements in the new test's Javadoc. Document how to skip this one test from the comment line in the Javadoc: mvn ... -Dtest='!ClassNameTest' - Document the above in the VOTE email and release notes. - Perhaps also document the threshold in the VOTE what constitutes acceptable coverage for RC: Java versions and OS types/versions. - The RM then decides if the threshold is met based on the VOTE replies
Gary On Sun, May 12, 2024 at 2:21 PM Thomas Vandahl <t...@apache.org> wrote: > > Hi folks, > > how shall we proceed with the release process? We have tests which rely on a > working multicast configuration. This seems to be a serious obstacle. I can > exclude the tests so that the build should be runnable by anyone. Downside > is, that we don't test the feature anymore. > > I'm a bit at a loss on how to tackle this problem. I'm open for suggestions. > Please help! > > Bye, Thomas > > > Am 05.05.2024 um 19:20 schrieb Thomas Vandahl <tho...@vandahl.org>: > > > > Hi Bruno, > > > >> Am 02.05.2024 um 22:01 schrieb Bruno Kinoshita <brunodepau...@gmail.com>: > >> > >> Tried building the project but alas I think my network has UDP multicast > >> issues? > >> > >> [ERROR] Failures: > >> [ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:122 > >> message not received > >> [ERROR] UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:150 > >> message not received > >> [ERROR] UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:175 > >> message not received > >> [ERROR] UDPDiscoverySenderUnitTest.testPassiveBroadcast:119 message not > >> received > >> [ERROR] UDPDiscoverySenderUnitTest.testRemoveBroadcast:149 message not > >> received > >> [ERROR] UDPDiscoverySenderUnitTest.testRequestBroadcast:176 message not > >> received > >> [ERROR] > >> UDPDiscoveryUnitTest.testSimpleUDPDiscoveryIPv4:49->simpleUDPDiscovery:131 > >> Receiver count [0] should be the at least the number sent [10]. > >> [INFO] > >> [ERROR] Tests run: 431, Failures: 7, Errors: 0, Skipped: 0 > > > > Yes, this means that multicast consistently does not work in your > > environment - for whatever reason. > > There are several test tools available to check for configuration problems, > > like for example this one: > > https://github.com/enclave-networks/multicast-test > > <https://github.com/enclave-networks/multicast-test> > > > > Could you please give it a try? > > > > Bye, Thomas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
