Hi Gary
> Am 07.04.2024 um 20:54 schrieb Gary D. Gregory :
>
> Hi Thomas,
>
> OK, here we go:
>
> VPN on (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for
> Windows x64)
> git checkout fe20ca994803b353c32fd0909621d822ee26263c
> mvn clean test
On Sun, 7 Apr 2024 at 17:51, Thomas Vandahl wrote:
>
> Hi Sebastian
>
> > Am 06.04.2024 um 15:38 schrieb sebb :
> >
> > Another minor issue:
> > If you run 'mvn test' without first doing 'mvn clean', it fails with:
> >
> > [ERROR] JDBCDiskCacheUnitTest.testInitializePoolAccess_withPoolName:157
Hi Thomas,
OK, here we go:
VPN on (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for
Windows x64)
git checkout fe20ca994803b353c32fd0909621d822ee26263c
mvn clean test -Dtest=UDPDiscoverySenderEncryptedUnitTest
Same 3 failures, log: https://paste.apache.org/grnpx
TY!
Gary
(trying to move this out of the vote thread)
Hi Gary,
> Am 07.04.2024 um 14:33 schrieb Gary D. Gregory :
>
> Hi Thomas,
>
> Ran:
>
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
>
> Log:
>
> https://paste.apache.org/1hmkb
Thank you. Could you please make sure that you are at commit
Hi Sebastian
> Am 06.04.2024 um 15:38 schrieb sebb :
>
> 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
Hi Thomas,
Ran:
mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
Log:
https://paste.apache.org/1hmkb
Gary
On 2024/04/06 20:06:47 Thomas Vandahl wrote:
> 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
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
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
Wow, that's the first macOS failure for this type of issue. Bruno and I
both see this on Windows.
Gary
On Fri, Apr 5, 2024, 4:22 PM Rob Tompkins wrote:
> Ah…pardon. Here’s my local info:
>
> % mvn -version
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home:
Ah…pardon. Here’s my local info:
% mvn -version
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /opt/homebrew/Cellar/maven/3.9.4/libexec
Java version: 17.0.9, vendor: Amazon.com Inc., runtime:
/Library/Java/JavaVirtualMachines/amazon-corretto-17.jdk/Contents/Home
Rob,
What OS and such (mvn -version)?
Gary
On 2024/04/05 14:51:39 Rob Tompkins wrote:
> -0.5: building with java17 from the src zip I get the following for the
> jcs-core module
>
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]
Thomas,
I checkout out the tag "commons-jcs3-3.2" BUT that tag is NOT read-only, as
opposed to where it should be: "rel/commons-jcs3-3.2" and ran "mvn clean
verify" and got failures on Windows that look the same as this RC:
[INFO] Running
-0.5: building with java17 from the src zip I get the following for the
jcs-core module
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 message
not received
[ERROR] UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:138
Hi Gary,
> Am 04.04.2024 um 22:30 schrieb Gary D. Gregory :
>
> After being successful on macOS, I am seeing the following _repeatable_
> failures on Windows 10 running the default Maven goal (just `mvn`):
>
> ...
> [INFO] Running
>
Hi Bruno,
> Am 04.04.2024 um 21:46 schrieb Bruno Kinoshita :
>
> Failed to collect
> dependencies at org.apache.openjpa:openjpa:jar:2.4.3 ->
> org.apache.openjpa:openjpa-kernel:jar:2.4.3 ->
> com.ibm.websphere:websphere_uow_api:jar:0.0.1: Failed to read artifact
> descriptor for
FTR, on Linux running inside Windows (WSL), the build works for me using:
Linux RS-PF3NRMLR 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home:
Understood, TY!
Gary
On Fri, Apr 5, 2024 at 2:26 AM Thomas Vandahl wrote:
>
> Hi Gary,
>
> > Am 04.04.2024 um 21:59 schrieb Gary Gregory :
> >
> > Note that the parent pom is way behind in versions but I am not sure
> > it matters here (aside from not getting JPMS modules almost for free).
>
>
Thank you for the clarification :-)
Gary
On Fri, Apr 5, 2024 at 2:24 AM Thomas Vandahl wrote:
>
> Hi Gary,
>
> > Am 04.04.2024 um 21:58 schrieb Gary Gregory :
> >
> > Hi Thomas,
> >
> > Thank you for preparing a release candidate.
> >
> > Something looks confusing in the source tree:
> >
> > In
I mean that the release notes text file are missing Jira IDs.
HTH,
Gary
On Fri, Apr 5, 2024, 2:36 AM Thomas Vandahl wrote:
> Hi Gary,
>
> > Am 04.04.2024 um 22:22 schrieb Gary Gregory :
> >
> > Another note:
> >
> > The changes.xml contains XML not supported by the VM file, for
> > example,
Hi Gary,
> Am 04.04.2024 um 22:22 schrieb Gary Gregory :
>
> Another note:
>
> The changes.xml contains XML not supported by the VM file, for
> example, all of the JIRA issue IDs are lost.
>
I see working JIRA links in
Hi Gary,
> Am 04.04.2024 um 22:05 schrieb Gary Gregory :
>
> I think it is better to keep the release notes as a _history_ instead
> of only the latest. This lets you see what you're getting when
> migrating from several versions back.
I don't quite get your point, I'm afraid. Isn't this what
Hi Gary,
> Am 04.04.2024 um 21:59 schrieb Gary Gregory :
>
> Note that the parent pom is way behind in versions but I am not sure
> it matters here (aside from not getting JPMS modules almost for free).
Yes, again: intentional. This being a bug fix release for 3.2, I did not want
to change too
Hi Gary,
> Am 04.04.2024 um 21:58 schrieb Gary Gregory :
>
> Hi Thomas,
>
> Thank you for preparing a release candidate.
>
> Something looks confusing in the source tree:
>
> In git master marked as version 3.2.2-SNAPSHOT, all of the Maven
> modules follow the normal naming convention where
After being successful on macOS, I am seeing the following _repeatable_
failures on Windows 10 running the default Maven goal (just `mvn`):
...
[INFO] Running
org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
[ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0,
Another note:
The changes.xml contains XML not supported by the VM file, for
example, all of the JIRA issue IDs are lost.
Gary
On Thu, Apr 4, 2024 at 10:52 AM Thomas Vandahl wrote:
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I
> would like to
This:
(file://${basedir}/internal-repository):
makes it look like a variable interpolation issue, maybe.
Can you try with Maven 3.9.6 (the latest).
Gary
On Thu, Apr 4, 2024 at 3:48 PM Bruno Kinoshita wrote:
>
> Hi Thomas,
>
> The build is not working for me. Are you able to tell me what
FWIW, I can run the default goal, IOW, just `mvn` on the command line.
Running `mvn clean install site` runs successfully using:
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
I think it is better to keep the release notes as a _history_ instead
of only the latest. This lets you see what you're getting when
migrating from several versions back.
Gary
On Thu, Apr 4, 2024 at 10:52 AM Thomas Vandahl wrote:
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons
Note that the parent pom is way behind in versions but I am not sure
it matters here (aside from not getting JPMS modules almost for free).
Gary
On Thu, Apr 4, 2024 at 3:48 PM Bruno Kinoshita wrote:
>
> Hi Thomas,
>
> The build is not working for me. Are you able to tell me what could be
>
Hi Thomas,
Thank you for preparing a release candidate.
Something looks confusing in the source tree:
In git master marked as version 3.2.2-SNAPSHOT, all of the Maven
modules follow the normal naming convention where directory names are
artifact IDs, for example, "commons-jcs3-core":
Hi Thomas,
The build is not working for me. Are you able to tell me what could be
wrong with my environment, please?
commit 0b20664b6c60b025cfe0e95c33e86f3239822a12 (HEAD, tag:
commons-jcs3-3.2.1-rc1)
Author: Thomas Vandahl
Date: Thu Apr 4 14:47:16 2024 +0200
[maven-release-plugin]
My vote:
> 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.
>
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should
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.
Apache Commons JCS 3.2.1 rc1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn revision
68312)
The Git tag
46 matches
Mail list logo
