You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Thomas Vandahl <tv...@apache.org> on 2021/12/23 18:20:59 UTC
[VOTE] Release Apache Commons JCS 3.1 based on RC1
Hi folks,
We have fixed quite a few bugs and added some significant enhancements since Apache Commons JCS 3.0 was released, so I would like to release Apache Commons JCS 3.1.
Apache Commons JCS 3.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1
The Git tag commons-jcs-3.1-rc1 commit for this RC is f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1575/org/apache/commons/commons-jcs3/3.1/
These are the distribution artifacts and their hashes:
commons-jcs3-dist-3.1-bin.tar.gz
651d9adaa7495a5411baf2903f57e1471633ba1742ce4739dd5060f186ddecfb44afe9b528eac1d904ebc8bfe43654a455fe8a6ccb0a46449acf2830ad3a015e
commons-jcs3-dist-3.1-bin.zip
5e53f4ddca4071aa9d13d88b17444afdcb71f513ab0cef1be4e5dd5162c477d101b50dbecb5a7624546fbd4985d1ca4024ab6f3ef1b06d6f0a3fbfea393ba861
commons-jcs3-dist-3.1-src.tar.gz
137639d251a52ebf61b15eb710b201c2d6f1b111c507596bd49ecee313ec1e51fd885ad869addebb337cceddb1eb9ab9e73e77baf705a7cbfaae3d9bd4251ec5
commons-jcs3-dist-3.1-src.zip
013f85fa8f291b4ea3f2b43858dd48bd3335a4092339971c8a6b16751ae7c539b031ac27897d800ee2e523d3e9edf776b7a8911a9adf8633e064b489ff8de2b9
I have tested this with ***'mvn clean install site'*** using:
---
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_241, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
---
Details of changes since 3.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/index.html
(note some *relative* links are broken and the 3.1 directories are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 3.0):
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Thomas Vandahl (tv),
Release Manager (using key 88817402)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Misses a 3 after "jcs" in branch name I think
Le jeu. 23 déc. 2021 à 20:05, Gary Gregory <ga...@gmail.com> a
écrit :
> git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch
> commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
> Cloning into 'commons-jcs-3.1-rc1'...
> fatal: Remote branch commons-jcs-3.1-rc1 not found in upstream origin
>
> ?
>
> Gary
>
> On Thu, Dec 23, 2021 at 1:21 PM Thomas Vandahl <tv...@apache.org> wrote:
>
> > Hi folks,
> >
> > We have fixed quite a few bugs and added some significant enhancements
> > since Apache Commons JCS 3.0 was released, so I would like to release
> > Apache Commons JCS 3.1.
> >
> > Apache Commons JCS 3.1 RC1 is available for review here:
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1
> >
> > The Git tag commons-jcs-3.1-rc1 commit for this RC is
> > f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here:
> >
> >
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
> >
> > You may checkout this tag using:
> > git clone https://gitbox.apache.org/repos/asf/commons-jcs.git
> > --branch commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
> >
> > Maven artifacts are here:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1575/org/apache/commons/commons-jcs3/3.1/
> >
> > These are the distribution artifacts and their hashes:
> >
> > commons-jcs3-dist-3.1-bin.tar.gz
> >
> >
> 651d9adaa7495a5411baf2903f57e1471633ba1742ce4739dd5060f186ddecfb44afe9b528eac1d904ebc8bfe43654a455fe8a6ccb0a46449acf2830ad3a015e
> > commons-jcs3-dist-3.1-bin.zip
> >
> >
> 5e53f4ddca4071aa9d13d88b17444afdcb71f513ab0cef1be4e5dd5162c477d101b50dbecb5a7624546fbd4985d1ca4024ab6f3ef1b06d6f0a3fbfea393ba861
> > commons-jcs3-dist-3.1-src.tar.gz
> >
> >
> 137639d251a52ebf61b15eb710b201c2d6f1b111c507596bd49ecee313ec1e51fd885ad869addebb337cceddb1eb9ab9e73e77baf705a7cbfaae3d9bd4251ec5
> > commons-jcs3-dist-3.1-src.zip
> >
> >
> 013f85fa8f291b4ea3f2b43858dd48bd3335a4092339971c8a6b16751ae7c539b031ac27897d800ee2e523d3e9edf776b7a8911a9adf8633e064b489ff8de2b9
> >
> > I have tested this with ***'mvn clean install site'*** using:
> > ---
> > Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> > Java version: 1.8.0_241, vendor: Oracle Corporation, runtime:
> > /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
> > Default locale: de_DE, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> > ---
> >
> > Details of changes since 3.0 are in the release notes:
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/RELEASE-NOTES.txt
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/changes-report.html
> >
> > Site:
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/index.html
> > (note some *relative* links are broken and the 3.1 directories are
> not
> > yet created - these will be OK once the site is deployed.)
> >
> > JApiCmp Report (compared to 3.0):
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/japicmp.html
> >
> > RAT Report:
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/rat-report.html
> >
> > KEYS:
> > https://www.apache.org/dist/commons/KEYS
> >
> > Please review the release candidate and vote.
> > This vote will close no sooner that 72 hours from now.
> >
> > [ ] +1 Release these artifacts
> > [ ] +0 OK, but...
> > [ ] -0 OK, but really should fix...
> > [ ] -1 I oppose this release because...
> >
> > Thank you,
> >
> > Thomas Vandahl (tv),
> > Release Manager (using key 88817402)
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Gary Gregory <ga...@gmail.com>.
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch
commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
Cloning into 'commons-jcs-3.1-rc1'...
fatal: Remote branch commons-jcs-3.1-rc1 not found in upstream origin
?
Gary
On Thu, Dec 23, 2021 at 1:21 PM Thomas Vandahl <tv...@apache.org> wrote:
> Hi folks,
>
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons JCS 3.0 was released, so I would like to release
> Apache Commons JCS 3.1.
>
> Apache Commons JCS 3.1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1
>
> The Git tag commons-jcs-3.1-rc1 commit for this RC is
> f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
>
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-jcs.git
> --branch commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1575/org/apache/commons/commons-jcs3/3.1/
>
> These are the distribution artifacts and their hashes:
>
> commons-jcs3-dist-3.1-bin.tar.gz
>
> 651d9adaa7495a5411baf2903f57e1471633ba1742ce4739dd5060f186ddecfb44afe9b528eac1d904ebc8bfe43654a455fe8a6ccb0a46449acf2830ad3a015e
> commons-jcs3-dist-3.1-bin.zip
>
> 5e53f4ddca4071aa9d13d88b17444afdcb71f513ab0cef1be4e5dd5162c477d101b50dbecb5a7624546fbd4985d1ca4024ab6f3ef1b06d6f0a3fbfea393ba861
> commons-jcs3-dist-3.1-src.tar.gz
>
> 137639d251a52ebf61b15eb710b201c2d6f1b111c507596bd49ecee313ec1e51fd885ad869addebb337cceddb1eb9ab9e73e77baf705a7cbfaae3d9bd4251ec5
> commons-jcs3-dist-3.1-src.zip
>
> 013f85fa8f291b4ea3f2b43858dd48bd3335a4092339971c8a6b16751ae7c539b031ac27897d800ee2e523d3e9edf776b7a8911a9adf8633e064b489ff8de2b9
>
> I have tested this with ***'mvn clean install site'*** using:
> ---
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_241, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> ---
>
> Details of changes since 3.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/index.html
> (note some *relative* links are broken and the 3.1 directories are not
> yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/rat-report.html
>
> KEYS:
> https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now.
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> Thank you,
>
> Thomas Vandahl (tv),
> Release Manager (using key 88817402)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [CANCEL][VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, Dec 31, 2021 at 4:25 AM Thomas Vandahl <tv...@apache.org> wrote:
> > Am 23.12.2021 um 19:20 schrieb Thomas Vandahl <tv...@apache.org>:
> >
> > Hi folks,
> >
> > We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons JCS 3.0 was released, so I would like to release
> Apache Commons JCS 3.1.
>
> Thanks to Bruno we were able to find an issue that could cause serious
> performance degradation in EncryptingSerializer. I will fix this and cut an
> RC2 rsn.
>
Great news! See you at RC2 time :-)
Gary
>
> Bye, Thomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
[CANCEL][VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl <tv...@apache.org>:
>
> Hi folks,
>
> We have fixed quite a few bugs and added some significant enhancements since Apache Commons JCS 3.0 was released, so I would like to release Apache Commons JCS 3.1.
Thanks to Bruno we were able to find an issue that could cause serious performance degradation in EncryptingSerializer. I will fix this and cut an RC2 rsn.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1 as well (tested on some apps and checked source bundle)
Le jeu. 23 déc. 2021 à 20:42, Thomas Vandahl <tv...@apache.org> a écrit :
> My vote:
>
> > Am 23.12.2021 um 19:20 schrieb Thomas Vandahl <tv...@apache.org>:
> >
> > [X] +1 Release these artifacts
> > [ ] +0 OK, but...
> > [ ] -0 OK, but really should fix...
> > [ ] -1 I oppose this release because...
>
> Bye, Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
My vote:
> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl <tv...@apache.org>:
>
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
Just remembered seeing some classes in JCS that had Blocking in the name. Maybe it is intentional to use that SecureRandom implementation.
In which case I think the best option would be to re-write the test that fails on environments where /dev/random is slow.
Cheers
Bruno
Sent from Yahoo Mail on Android
On Fri, 31 Dec 2021 at 10:05, Bruno P. Kinoshita<br...@yahoo.com.br.INVALID> wrote: Hi,
Thomas has had a lot of patience troubleshooting this issue with me off-list (thanks heaps!). Not only remotely, but I think we are on opposite timezones too.
Yesterday Thomas suggested to look at EncryptingSerializer, and also to look at the time that my machine was taking to get data from /dev/random. Turns out that was a good suggestion, as /dev/random is very slow on my old Thinkpad (maybe some daemon that I disabled, or another BIOS/OS setting?.
It never caused any issue on my environment - that I could notice, at least. But for Commons JCS the unit tests take a very long time to run. The call to this.secureRandom.nextBytes() in EncryptingSerializer takes about 1 minute.
I configured my JVM with the java.security configuration file to use /dev/urandom, but the tests still failed. Tried /dev/./urandom (found it in some Tomcat docs) but it made not difference.
Looking at EncrytpingSerializer, it calls SecureRandom.getInstanceStrong(). With a debugger, I confirmed that it returned a NativePRNGBlocking, which states in its docs that it uses /dev/random. Changing that to `this.secureRandom = new SecureRandom()` the tests for me pass with `mvn clean test install site` in 5-6 minutes, with no issues.
I had a quick look at commons-rng, and saw that it uses `SecureRandom secureRandom = new SecureRandom()`. Looking at that constructor docs, it appears that it chooses the best random generator based on the list of available providers. So maybe replacing `SecureRandom.getInstanceStrong` by `new SecureRandom()`, and documenting to users that they must specify the best option for their environment, preferably one that generates random-enough data, could be an improvement for a next release? (didn't have time to dig more and see the implications of doing so, maybe others here have more experience, other ideas?)
I didn't have time to look if that `.getInstanceStrong` was introduced in this release, but if not, and since no users are reporting any issues with that, I guess it is not a blocker? Assuming that's correct, I'll leave my +1 here.
And thank you again, Thomas!
Cheers
Bruno
On Thursday, 30 December 2021, 04:12:03 am NZDT, Thomas Vandahl <tv...@apache.org> wrote:
> Am 29.12.2021 um 16:06 schrieb Gary Gregory <ga...@gmail.com>:
>
> Is this test failure being addressed?
Well, "addressed" is a big word for what I'm currently trying. "looked at" is closer to what happens.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
Hi,
Thomas has had a lot of patience troubleshooting this issue with me off-list (thanks heaps!). Not only remotely, but I think we are on opposite timezones too.
Yesterday Thomas suggested to look at EncryptingSerializer, and also to look at the time that my machine was taking to get data from /dev/random. Turns out that was a good suggestion, as /dev/random is very slow on my old Thinkpad (maybe some daemon that I disabled, or another BIOS/OS setting?.
It never caused any issue on my environment - that I could notice, at least. But for Commons JCS the unit tests take a very long time to run. The call to this.secureRandom.nextBytes() in EncryptingSerializer takes about 1 minute.
I configured my JVM with the java.security configuration file to use /dev/urandom, but the tests still failed. Tried /dev/./urandom (found it in some Tomcat docs) but it made not difference.
Looking at EncrytpingSerializer, it calls SecureRandom.getInstanceStrong(). With a debugger, I confirmed that it returned a NativePRNGBlocking, which states in its docs that it uses /dev/random. Changing that to `this.secureRandom = new SecureRandom()` the tests for me pass with `mvn clean test install site` in 5-6 minutes, with no issues.
I had a quick look at commons-rng, and saw that it uses `SecureRandom secureRandom = new SecureRandom()`. Looking at that constructor docs, it appears that it chooses the best random generator based on the list of available providers. So maybe replacing `SecureRandom.getInstanceStrong` by `new SecureRandom()`, and documenting to users that they must specify the best option for their environment, preferably one that generates random-enough data, could be an improvement for a next release? (didn't have time to dig more and see the implications of doing so, maybe others here have more experience, other ideas?)
I didn't have time to look if that `.getInstanceStrong` was introduced in this release, but if not, and since no users are reporting any issues with that, I guess it is not a blocker? Assuming that's correct, I'll leave my +1 here.
And thank you again, Thomas!
Cheers
Bruno
On Thursday, 30 December 2021, 04:12:03 am NZDT, Thomas Vandahl <tv...@apache.org> wrote:
> Am 29.12.2021 um 16:06 schrieb Gary Gregory <ga...@gmail.com>:
>
> Is this test failure being addressed?
Well, "addressed" is a big word for what I'm currently trying. "looked at" is closer to what happens.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
> Am 29.12.2021 um 16:06 schrieb Gary Gregory <ga...@gmail.com>:
>
> Is this test failure being addressed?
Well, "addressed" is a big word for what I'm currently trying. "looked at" is closer to what happens.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Gary Gregory <ga...@gmail.com>.
FWIW, from the git tag, I run 'mvn clean install' and it passes but I think
we should make it easier to make reviewers pass builds since we do not
always have a lot of reviewers ;-)
Is this test failure being addressed?
TY!
Gary
PS: My set up is:
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-bre_2021_10_20_23_15-b00)
OpenJDK 64-Bit Server VM (build 25.312-b00, mixed mode)
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /usr/local/Cellar/maven/3.8.4/libexec
Java version: 1.8.0_312, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+312/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "12.1", arch: "x86_64", family: "mac"
Darwin *** 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST
2021; root:xnu-8019.61.5~1/RELEASE_X86_64 x86_64
GG
On Tue, Dec 28, 2021 at 11:44 AM Thomas Vandahl <tv...@apache.org> wrote:
> > Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita <
> brunodepaulak@yahoo.com.br.INVALID>:
> >
> > `mvn clean test install site` took a few minutes, but it just finished
> running. Below the error that just happened again on my environment
> (appears to be consistent for me):
> >
> > [INFO] Results:
> > [INFO]
> > [ERROR] Failures:
> > [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be
> null, Region Name = blockRegion2
>
> Can you send me the log file please (direct mail, supposed to be in
> target/) If the test fails consistently, please run just that test because
> the log file is being overwritten every time.
>
> > [INFO] Apache Commons JCS :: Core ......................... FAILURE
> [17:44 min]
>
> =:-o That's actually a *lot* of time. My seven year old Macbook needs
> about four minutes for the same task. Maybe there's a timing issue.
>
> Bye, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
Sent off-list. Used GMail for my @apache.org email (too lazy to migrate all my yahoo subscriptions over there). It has a zip attachment, so not sure if it will be in your inbox or spam folder, but it should arrive in a few minutes/hours.
Cheers
Bruno
On Wednesday, 29 December 2021, 05:44:31 am NZDT, Thomas Vandahl <tv...@apache.org> wrote:
> Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita <br...@yahoo.com.br.INVALID>:
>
> `mvn clean test install site` took a few minutes, but it just finished running. Below the error that just happened again on my environment (appears to be consistent for me):
>
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
Can you send me the log file please (direct mail, supposed to be in target/) If the test fails consistently, please run just that test because the log file is being overwritten every time.
> [INFO] Apache Commons JCS :: Core ......................... FAILURE [17:44 min]
=:-o That's actually a *lot* of time. My seven year old Macbook needs about four minutes for the same task. Maybe there's a timing issue.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
> Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita <br...@yahoo.com.br.INVALID>:
>
> `mvn clean test install site` took a few minutes, but it just finished running. Below the error that just happened again on my environment (appears to be consistent for me):
>
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
Can you send me the log file please (direct mail, supposed to be in target/) If the test fails consistently, please run just that test because the log file is being overwritten every time.
> [INFO] Apache Commons JCS :: Core ......................... FAILURE [17:44 min]
=:-o That's actually a *lot* of time. My seven year old Macbook needs about four minutes for the same task. Maybe there's a timing issue.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
Hi Thomas,
I'm using my old Thinkpad, with Ubuntu LTS 20.04, JDK 11 and Maven 3.8.
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-91-generic", arch: "amd64", family: "unix"
Other than that, language is en_US, but I also have a few things in en_UK. Time Zone is NZ daylight saving time. That's all I can think of differences in my env.
Here's my git working copy details:
kinow@ranma:~/Development/java/apache/commons-jcs$ git status
HEAD detached at commons-jcs3-3.1-rc1
nothing to commit, working tree clean
kinow@ranma:~/Development/java/apache/commons-jcs$ git log -n 1
commit f370adb43aeef51a5456d93f13f2601f3b87c44a (HEAD, tag: commons-jcs3-3.1-rc1)
Author: Thomas Vandahl <tv...@apache.org>
Date: Thu Dec 23 18:20:21 2021 +0100
[maven-release-plugin] prepare release commons-jcs3-3.1-rc1
Hopefully I am using the correct branch. A little past midnight here, calling it a day now, just wanted to run the test and reply your message before doing so.
`mvn clean test install site` took a few minutes, but it just finished running. Below the error that just happened again on my environment (appears to be consistent for me):
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
HitCountRam = 0
HitCountAux = 0
---------------------------Memory Cache
Put Count = 0
Hit Count = 0
Miss Count = 1
Map Size = 0
List Size = 0
---------------------------Block Disk Cache
Is Alive = true
Key Map Size = 0
Data File Length = 0
Block Size Bytes = 4096
Number Of Blocks = 0
Average Put Size Bytes = 0
Empty Blocks = 0
Purgatory Hits = 0
Purgatory Size = 0
Working = true
Empty = true
Queue Size = 0
Queue Capacity = 2147483647
[INFO]
[ERROR] Tests run: 419, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Commons JCS 3.1:
[INFO]
[INFO] Apache Commons JCS ................................. SUCCESS [ 27.301 s]
[INFO] Apache Commons JCS :: Core ......................... FAILURE [17:44 min]
[INFO] Apache Commons JCS :: JCache ....................... SKIPPED
[INFO] Apache Commons JCS :: JCache TCK ................... SKIPPED
[INFO] Apache Commons JCS :: JCache Extras ................ SKIPPED
[INFO] Apache Commons JCS :: JCache OpenJPA ............... SKIPPED
[INFO] Apache Commons JCS :: Distribution ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18:11 min
[INFO] Finished at: 2021-12-29T00:56:27+13:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project commons-jcs3-core: There are test failures.
-Bruno
On Tuesday, 28 December 2021, 11:08:47 pm NZDT, Thomas Vandahl <tv...@apache.org> wrote:
Hi Bruno.
> Am 24.12.2021 um 02:00 schrieb Bruno P. Kinoshita <br...@yahoo.com.br.INVALID>:
>
> [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
Can you reproduce the failure (because I can't)? Some of the concurrent tests are timing sensitive. If you can reproduce the failure situation, I would be very much interested in your test setup.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Bruno.
> Am 24.12.2021 um 02:00 schrieb Bruno P. Kinoshita <br...@yahoo.com.br.INVALID>:
>
> [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
Can you reproduce the failure (because I can't)? Some of the concurrent tests are timing sensitive. If you can reproduce the failure situation, I would be very much interested in your test setup.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
Hi,
I couldn't find the tag "commons-jcs-3.1-rc1", I think the tag is "commons-jcs3-3.1-rc1" (missing 3 after jcs)?
Building from that tag on:
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-91-generic", arch: "amd64", family: "unix"
with `mvn clean test install site` had one test failing:
[INFO]
[ERROR] Failures:
[ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, Region Name = blockRegion2
HitCountRam = 0
HitCountAux = 0
---------------------------Memory Cache
Put Count = 0
Hit Count = 0
Miss Count = 1
Map Size = 0
List Size = 0
---------------------------Block Disk Cache
Is Alive = true
Key Map Size = 0
Data File Length = 0
Block Size Bytes = 4096
Number Of Blocks = 0
Average Put Size Bytes = 0
Empty Blocks = 0
Purgatory Hits = 0
Purgatory Size = 0
Working = true
Empty = true
Queue Size = 0
Queue Capacity = 2147483647
[INFO]
[ERROR] Tests run: 419, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Commons JCS 3.1:
[INFO]
[INFO] Apache Commons JCS ................................. SUCCESS [03:34 min]
[INFO] Apache Commons JCS :: Core ......................... FAILURE [ 01:43 h]
[INFO] Apache Commons JCS :: JCache ....................... SKIPPED
[INFO] Apache Commons JCS :: JCache TCK ................... SKIPPED
[INFO] Apache Commons JCS :: JCache Extras ................ SKIPPED
[INFO] Apache Commons JCS :: JCache OpenJPA ............... SKIPPED
[INFO] Apache Commons JCS :: Distribution ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:46 h
[INFO] Finished at: 2021-12-24T13:12:42+13:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project commons-jcs3-core: There are test failures.
Bruno
On Friday, 24 December 2021, 07:21:08 am NZDT, Thomas Vandahl <tv...@apache.org> wrote:
Hi folks,
We have fixed quite a few bugs and added some significant enhancements since Apache Commons JCS 3.0 was released, so I would like to release Apache Commons JCS 3.1.
Apache Commons JCS 3.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1
The Git tag commons-jcs-3.1-rc1 commit for this RC is f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch commons-jcs-3.1-rc1 commons-jcs-3.1-rc1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1575/org/apache/commons/commons-jcs3/3.1/
These are the distribution artifacts and their hashes:
commons-jcs3-dist-3.1-bin.tar.gz
651d9adaa7495a5411baf2903f57e1471633ba1742ce4739dd5060f186ddecfb44afe9b528eac1d904ebc8bfe43654a455fe8a6ccb0a46449acf2830ad3a015e
commons-jcs3-dist-3.1-bin.zip
5e53f4ddca4071aa9d13d88b17444afdcb71f513ab0cef1be4e5dd5162c477d101b50dbecb5a7624546fbd4985d1ca4024ab6f3ef1b06d6f0a3fbfea393ba861
commons-jcs3-dist-3.1-src.tar.gz
137639d251a52ebf61b15eb710b201c2d6f1b111c507596bd49ecee313ec1e51fd885ad869addebb337cceddb1eb9ab9e73e77baf705a7cbfaae3d9bd4251ec5
commons-jcs3-dist-3.1-src.zip
013f85fa8f291b4ea3f2b43858dd48bd3335a4092339971c8a6b16751ae7c539b031ac27897d800ee2e523d3e9edf776b7a8911a9adf8633e064b489ff8de2b9
I have tested this with ***'mvn clean install site'*** using:
---
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_241, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
---
Details of changes since 3.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/index.html
(note some *relative* links are broken and the 3.1 directories are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 3.0):
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Thomas Vandahl (tv),
Release Manager (using key 88817402)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
Yeah, sorry - typo.
> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl <tv...@apache.org>:
>
> The Git tag commons-jcs3-3.1-rc1 commit for this RC is f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here:
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
>
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch commons-jcs3-3.1-rc1 commons-jcs3-3.1-rc1
Sorry for the confusion.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org