Hi Gary,
> Am 06.04.2024 um 17:20 schrieb Gary D. Gregory :
>
> Switching to origin/release-3.2.1 lets me run the default Maven goal (just
> 'mvn') to successfully to completion!
>
May I kindly ask for the debug log again? I'd like to know whether JCS can find
a valid multicast interface
Hi Gary,
> Am 06.04.2024 um 19:35 schrieb Gary Gregory :
>
> This is where you want to use JUnit assumptions so you get visibility for
> skipped tests.
>
Yes, I know. However, that does not work with the old JUnit3-style tests. I
will fix this in the master branch where all tests already have
This is where you want to use JUnit assumptions so you get visibility for
skipped tests.
Gary
On Sat, Apr 6, 2024, 12:54 PM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> tv pushed a commit to branch release-3.2.1
> in repository
Probably a job for JUnit assumptions.
Gary
On Sat, Apr 6, 2024, 12:17 PM Thomas Vandahl wrote:
> Hi Gary,
>
> > Am 06.04.2024 um 17:48 schrieb Gary D. Gregory :
> >
> > And to confirm that VPN is the issue, I reconnected and got:
> >
> > [ERROR] Failures:
> > [ERROR]
Hi Gary,
> Am 06.04.2024 um 17:48 schrieb Gary D. Gregory :
>
> And to confirm that VPN is the issue, I reconnected and got:
>
> [ERROR] Failures:
> [ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116
> message not received
> [ERROR]
And to confirm that VPN is the issue, I reconnected and got:
[ERROR] Failures:
[ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 message
not received
[ERROR] UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:138 message
not received
[ERROR]
Hi Gary,
> Am 06.04.2024 um 17:20 schrieb Gary D. Gregory :
>
> Ah, I was on git master on Windows, which without the VPN, now hangs in:
>
> [INFO] Running
> org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCacheConcurrentNoDeadLockUnitTest
>
Thou shalt not run the whole test suite
Ah, I was on git master on Windows, which without the VPN, now hangs in:
[INFO] Running
org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCacheConcurrentNoDeadLockUnitTest
Switching to origin/release-3.2.1 lets me run the default Maven goal (just
'mvn') to successfully to completion!
Hi Gary,
> Am 06.04.2024 um 15:07 schrieb Gary D. Gregory :
>
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
>
> which failed with the log here: https://paste.apache.org/b4p09
Please check out from branch release-3.2.1 and try again.
Bye, Thomas
Hi Gary,
> Am 06.04.2024 um 15:07 schrieb Gary D. Gregory :
>
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
>
> which failed with the log here: https://paste.apache.org/b4p09
Thanks for helping me to tackle this. I see that the network interface used for
the test is a "Cisco
Another minor issue:
If you run 'mvn test' without first doing 'mvn clean', it fails with:
[ERROR] JDBCDiskCacheUnitTest.testInitializePoolAccess_withPoolName:157
» SQL Table already exists: JCSTESTTABLE_INITIALIZEPOOLACCESS in
statement [CREATE CACHED TABLE JCSTESTTABLE_InitializePoolAccess]
Thomas,
Running 'mvn clean verify -pl commons-jcs3-core' fails as usual (git master).
The class UDPDiscoverySenderUnitTest is _excluded_ in the POM so it does not
even run.
I edited logging.properties:
handlers=java.util.logging.FileHandler
.level = FINER
Hi Gary,
> Am 06.04.2024 um 14:10 schrieb Gary D. Gregory :
>
> Hi Thomas,
>
> I ran:
>
> mvn test -Dtest=UDPDiscoverySenderUnitTest -X >\test\out.txt
>
> and killed it after 10 minutes since it never finished. I tried 3 times.
Thanks. Not good.
Could you please repeat the test with the log
Hi Thomas,
I ran:
mvn test -Dtest=UDPDiscoverySenderUnitTest -X >\test\out.txt
and killed it after 10 minutes since it never finished. I tried 3 times.
See https://paste.apache.org/0d08b
TY,
Gary
On 2024/04/06 10:02:36 Thomas Vandahl wrote:
> Hi Gary,
>
> > Am 05.04.2024 um 17:28 schrieb
Hi Gary,
> Am 05.04.2024 um 17:28 schrieb Gary D. Gregory :
>
> [INFO] Running
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
> [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 9.526
> s <<< FAILURE! - in
>
I am cancelling the vote because of strange test failures in some environments.
Bye, Thomas
> Am 04.04.2024 um 16:49 schrieb Thomas Vandahl :
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I
> would like to release Apache Commons JCS 3.2.1.
>
>
Hi folks,
> Am 05.04.2024 um 23:26 schrieb Gary Gregory :
>
> Wow, that's the first macOS failure for this type of issue. Bruno and I
> both see this on Windows.
Ok, let's try to fix this. Could you please run the affected test only with
debug log and provide the log files to me?
I'll cancel
17 matches
Mail list logo
