date:20180206

[VOTE] Release JMeter 4.0 RC7

2018-02-06 Thread Milamber

Hello,

The seventh release candidate for JMeter 4.0 (r1823414) has been
prepared, and your votes are solicited.

This release brings a new default theme (Darcula), support for Java 9,
74 enhancements (new features and improvements), and 26 bug fixes.

Please, test this release candidate (with load tests and/or functional
tests) using Java 8 or 9 on Linux/Windows/Mac OS, especially on the
changes. Feedback is very welcome within the next 72 hours.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-4.0RC7/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version targets Java 8 / 9.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v4.0_RC7/
(dist revision r24781)

RAT report:

http://home.apache.org/~milamber/jmeter-4.0RC7/dist/rat-report-jmeter-4.0RC7.txt

MD5 hashes of archives for this vote:

bfd202f5eb8a0ac322a145b97ef3fded *apache-jmeter-4.0.tgz
3a84491f10fb7b147101cf3926c4a855 *apache-jmeter-4.0.zip
7b3ed61896d704f3307d800616272393 *apache-jmeter-4.0_src.tgz
2f8d4260f125925eacce1069b295f53c *apache-jmeter-4.0_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-4.0RC7/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1028/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v4_0_RC7/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 4.0 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-4.0RC7/docs/changes.html#Known%20problems%20and%20workarounds

All feedback and vote are welcome.

[ ] +1 I support this release
[ ] +0 I am OK with this release
[ ] -0 OK, but
[ ] -1 I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.

Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

*Note:* the RC1, RC2 and RC3 were not submit for vote due an issue in
release process when the maven artefacts are upload to nexus. For this
RC7, the automatic maven upload inside build.xml was replaced by a
semi-automatic upload with the maven-gpg-plugin.

*Note2:* the RC5 were not submit for vote due an little commit by
Philippe :-) during the release process.

Re: svn commit: r1823414 - in /jmeter/tags/v4_0_RC7: ./ build.xml

2018-02-06 Thread Milamber


Hello,

New day, I've changes my Internet connection from my hotel to my mobile 
data, and it's good now. Process release for RC7 under processing.


Milamber

On 07/02/2018 01:34, Milamber wrote:


I have an issue with the test Bug60607.jmx about DNS resolution. I'm 
not sure if that come with my current Internet connection (from my 
hotel) or a real bug.

Tired, so reported to next day.






batchtest:
 [echo] Starting Bug60607 with file Bug60607.jmx using -X 
-Jdummy=dummy

   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/home/milamber/temp/jmetertemp/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/home/milamber/temp/jmetertemp/lib/opt/activemq-all-5.15.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See 
http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]

   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/Bug60607.jmx
   [jmeter] Starting the test @ Wed Feb 07 01:30:02 CET 2018 
(1517963402627)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message 
on port 4445
   [jmeter] summary +  1 in 00:00:01 =1.9/s Avg:   438 Min:   
438 Max:   438 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary +  1 in 00:00:00 =8.1/s Avg:   117 Min:   
117 Max:   117 Err: 1 (100.00%) Active: 0 Started: 2 Finished: 2
   [jmeter] summary =  2 in 00:00:01 =3.0/s Avg:   277 Min:   
117 Max:   438 Err: 1 (50.00%)
   [jmeter] Tidying up ...@ Wed Feb 07 01:30:03 CET 2018 
(1517963403722)

   [jmeter] ... end of run

BUILD FAILED
/home/milamber/temp/jmetertemp/build.xml:2932: The following error 
occurred while executing this line:
/home/milamber/temp/jmetertemp/build.xml:2778: CSV Files are not 
identical.

/home/milamber/temp/jmetertemp/bin/testfiles/Bug60607.csv
label,responseCode,responseMessage,threadName,dataType,success
HTTP Request,200,OK,Thread Group 1-1,text,true
HTTP Request,Non HTTP response code: java.net.UnknownHostException,Non 
HTTP response message: Failed to resolve host name: 
jmeter.apache.org,Thread Group 2-1,text,true


/home/milamber/temp/jmetertemp/bin/Bug60607.csv
label,responseCode,responseMessage,threadName,dataType,success
HTTP Request,200,OK,Thread Group 1-1,text,true
HTTP Request,200,OK,Thread Group 2-1,text,false





On 07/02/2018 00:33, milam...@apache.org wrote:

Author: milamber
Date: Tue Feb  6 23:33:48 2018
New Revision: 1823414

URL: http://svn.apache.org/viewvc?rev=1823414=rev
Log:
Tag for pre-release

Added:
 jmeter/tags/v4_0_RC7/   (props changed)
   - copied from r1823413, jmeter/trunk/
Modified:
 jmeter/tags/v4_0_RC7/build.xml

Propchange: jmeter/tags/v4_0_RC7/
-- 


 bugtraq:append = true

Propchange: jmeter/tags/v4_0_RC7/
-- 


 bugtraq:label = Bugzilla Id:

Propchange: jmeter/tags/v4_0_RC7/
-- 


 bugtraq:message = Bugzilla Id: %BUGID%

Propchange: jmeter/tags/v4_0_RC7/
-- 


 bugtraq:number = true

Propchange: jmeter/tags/v4_0_RC7/
-- 

 bugtraq:url = 
https://issues.apache.org/bugzilla/show_bug.cgi?id=%BUGID%


Propchange: jmeter/tags/v4_0_RC7/
-- 


 bugtraq:warnifnoissue = true

Propchange: jmeter/tags/v4_0_RC7/
-- 


--- subclipse:tags (added)
+++ subclipse:tags Tue Feb  6 23:33:48 2018
@@ -0,0 +1,12 @@
+786921,v2_3_4,/jakarta/jmeter/tags/v2_3_4,tag
+963900,v2_4,/jakarta/jmeter/tags/v2_4,tag
+1158837,v2_5,/jakarta/jmeter/tags/v2_5,tag
+1178482,v2_5_1,/jakarta/jmeter/tags/v2_5_1,tag
+1195995,trunk,/jakarta/jmeter/trunk,tag
+1239301,v2_6,/jmeter/tags/v2_6,tag
+1343100,v2_7,/jmeter/tags/v2_7,tag
+1394743,v2_8,/jmeter/tags/v2_8,tag
+1439122,v2_9,/jmeter/tags/v2_9,tag
+1533926,v2_10,/jmeter/tags/v2_10,tag
+1555346,v2_11,/jmeter/tags/v2_11,tag
+1666551,v2_13,/jmeter/tags/v2_13,tag

Propchange: jmeter/tags/v4_0_RC7/
-- 


--- svn:ignore (added)
+++ svn:ignore Tue Feb  6 23:33:48 2018
@@ -0,0 +1,19 @@
+*.log
+build
+dist
+site
+printable_docs
+jmeter-fb.*
+.classpath
+.project
+.externalToolBuilders
+.settings
+reports
+local
+.checkstyle
+.fbwarnings
+.fbprefs
+.pmd
+build-local.properties
+target
+backups

Propchange: jmeter/tags/v4_0_RC7/

Re: svn commit: r1823414 - in /jmeter/tags/v4_0_RC7: ./ build.xml

2018-02-06 Thread Milamber



I have an issue with the test Bug60607.jmx about DNS resolution. I'm not 
sure if that come with my current Internet connection (from my hotel) or 
a real bug.

Tired, so reported to next day.






batchtest:
 [echo] Starting Bug60607 with file Bug60607.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/home/milamber/temp/jmetertemp/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/home/milamber/temp/jmetertemp/lib/opt/activemq-all-5.15.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See 
http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]

   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/Bug60607.jmx
   [jmeter] Starting the test @ Wed Feb 07 01:30:02 CET 2018 
(1517963402627)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message 
on port 4445
   [jmeter] summary +  1 in 00:00:01 =1.9/s Avg:   438 Min:   
438 Max:   438 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary +  1 in 00:00:00 =8.1/s Avg:   117 Min:   
117 Max:   117 Err: 1 (100.00%) Active: 0 Started: 2 Finished: 2
   [jmeter] summary =  2 in 00:00:01 =3.0/s Avg:   277 Min:   
117 Max:   438 Err: 1 (50.00%)
   [jmeter] Tidying up ...@ Wed Feb 07 01:30:03 CET 2018 
(1517963403722)

   [jmeter] ... end of run

BUILD FAILED
/home/milamber/temp/jmetertemp/build.xml:2932: The following error 
occurred while executing this line:

/home/milamber/temp/jmetertemp/build.xml:2778: CSV Files are not identical.
/home/milamber/temp/jmetertemp/bin/testfiles/Bug60607.csv
label,responseCode,responseMessage,threadName,dataType,success
HTTP Request,200,OK,Thread Group 1-1,text,true
HTTP Request,Non HTTP response code: java.net.UnknownHostException,Non 
HTTP response message: Failed to resolve host name: 
jmeter.apache.org,Thread Group 2-1,text,true


/home/milamber/temp/jmetertemp/bin/Bug60607.csv
label,responseCode,responseMessage,threadName,dataType,success
HTTP Request,200,OK,Thread Group 1-1,text,true
HTTP Request,200,OK,Thread Group 2-1,text,false





On 07/02/2018 00:33, milam...@apache.org wrote:

Author: milamber
Date: Tue Feb  6 23:33:48 2018
New Revision: 1823414

URL: http://svn.apache.org/viewvc?rev=1823414=rev
Log:
Tag for pre-release

Added:
 jmeter/tags/v4_0_RC7/   (props changed)
   - copied from r1823413, jmeter/trunk/
Modified:
 jmeter/tags/v4_0_RC7/build.xml

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:append = true

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:label = Bugzilla Id:

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:message = Bugzilla Id: %BUGID%

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:number = true

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:url = https://issues.apache.org/bugzilla/show_bug.cgi?id=%BUGID%

Propchange: jmeter/tags/v4_0_RC7/
--
 bugtraq:warnifnoissue = true

Propchange: jmeter/tags/v4_0_RC7/
--
--- subclipse:tags (added)
+++ subclipse:tags Tue Feb  6 23:33:48 2018
@@ -0,0 +1,12 @@
+786921,v2_3_4,/jakarta/jmeter/tags/v2_3_4,tag
+963900,v2_4,/jakarta/jmeter/tags/v2_4,tag
+1158837,v2_5,/jakarta/jmeter/tags/v2_5,tag
+1178482,v2_5_1,/jakarta/jmeter/tags/v2_5_1,tag
+1195995,trunk,/jakarta/jmeter/trunk,tag
+1239301,v2_6,/jmeter/tags/v2_6,tag
+1343100,v2_7,/jmeter/tags/v2_7,tag
+1394743,v2_8,/jmeter/tags/v2_8,tag
+1439122,v2_9,/jmeter/tags/v2_9,tag
+1533926,v2_10,/jmeter/tags/v2_10,tag
+1555346,v2_11,/jmeter/tags/v2_11,tag
+1666551,v2_13,/jmeter/tags/v2_13,tag

Propchange: jmeter/tags/v4_0_RC7/
--
--- svn:ignore (added)
+++ svn:ignore Tue Feb  6 23:33:48 2018
@@ -0,0 +1,19 @@
+*.log
+build
+dist
+site
+printable_docs
+jmeter-fb.*
+.classpath
+.project
+.externalToolBuilders
+.settings
+reports
+local
+.checkstyle
+.fbwarnings
+.fbprefs
+.pmd
+build-local.properties
+target
+backups

Propchange: jmeter/tags/v4_0_RC7/
--
 svn:mergeinfo = /jmeter/branches/docs-3.2:1792287,1792316

Modified: jmeter/tags/v4_0_RC7/build.xml
URL:

Jenkins build is back to normal : JMeter Windows #1012

2018-02-06 Thread Apache Jenkins Server

See

Jenkins build is back to normal : JMeter-trunk #6657

2018-02-06 Thread Apache Jenkins Server

See

Build failed in Jenkins: JMeter Ubuntu #405

2018-02-06 Thread Apache Jenkins Server

See 

--
[...truncated 9.72 KB...]
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1724)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:421)
Retrying after 10 seconds
Reverting  to depth 
infinity with ignoreExternals: false
ERROR: Failed to update http://svn.apache.org/repos/asf/jmeter/trunk
org.tmatesoft.svn.core.SVNException: svn: E200030: FULL
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.createSqlJetError(SVNSqlJetDb.java:195)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.beginTransaction(SVNSqlJetDb.java:211)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:257)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:252)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.obtainWCLock(SVNWCDb.java:5867)
at 
org.tmatesoft.svn.core.internal.wc17.SVNWCContext.acquireWriteLock(SVNWCContext.java:1646)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRevert.run(SvnNgRevert.java:37)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRevert.run(SvnNgRevert.java:26)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNWCClient.doRevert(SVNWCClient.java:1815)
at 
hudson.scm.subversion.UpdateWithRevertUpdater$TaskImpl.preUpdate(UpdateWithRevertUpdater.java:63)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:153)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168)
at 
hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1030)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1006)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:979)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
at hudson.remoting.UserRequest.perform(UserRequest.java:207)
at hudson.remoting.UserRequest.perform(UserRequest.java:53)
at hudson.remoting.Request$2.run(Request.java:358)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.tmatesoft.sqljet.core.SqlJetException: FULL: error code is FULL
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.openJournal(SqlJetPager.java:3051)
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.begin(SqlJetPager.java:2782)
at 
org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.beginTrans(SqlJetBtree.java:931)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.doBeginTransaction(SqlJetEngine.java:561)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.access$100(SqlJetEngine.java:55)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$9.runSynchronized(SqlJetEngine.java:475)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.beginTransaction(SqlJetEngine.java:471)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.beginTransaction(SVNSqlJetDb.java:206)
... 26 more
ERROR: Subversion update failed
org.tmatesoft.sqljet.core.SqlJetException: FULL: error code is FULL
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.openJournal(SqlJetPager.java:3051)
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.begin(SqlJetPager.java:2782)
at 
org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.beginTrans(SqlJetBtree.java:931)
at

[GitHub] jmeter pull request #341: Test isIgnore after post processor and assertions

2018-02-06 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/341


---

[GitHub] jmeter issue #374: Add a 'go to top' button that gets shown, when page is sc...

2018-02-06 Thread pmouawad

Github user pmouawad commented on the issue:

https://github.com/apache/jmeter/pull/374
  
Hi Felix,
Why not commit this before release ?
Do you have a doubt about it ?
Thanks



---

Bug 62082: __groovy function seems to have useless synchronized in execute

2018-02-06 Thread Philippe Mouawad

Hello,
What are you thought on this ?

Regards
Philippe

On Tue, Feb 6, 2018 at 9:09 PM,  wrote:

> https://bz.apache.org/bugzilla/show_bug.cgi?id=62082
>
> Bug ID: 62082
>Summary: __groovy function seems to have useless synchronized
> in execute
>Product: JMeter
>Version: 3.3
>   Hardware: All
> OS: All
> Status: NEW
>   Severity: enhancement
>   Priority: P2
>  Component: Main
>   Assignee: iss...@jmeter.apache.org
>   Reporter: p.moua...@ubik-ingenierie.com
>   Target Milestone: ---
>
> Following same analysis of Bug 57114 and as per understanding of this:
>
> -
> https://stackoverflow.com/questions/48644849/is-groovy-
> scriptingengine-thread-safe
>
> Groovy ScriptEngine "THREADING" is equal to MULTITHREADED:
> -
> https://docs.oracle.com/javase/8/docs/api/javax/
> script/ScriptEngineFactory.html#getParameter-java.lang.String-
>
> It seems we could avoid the synchronized block.
>
> Thoughts ?
> Thanks
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.




-- 
Cordialement.
Philippe Mouawad.

Re: [VOTE] Release JMeter 4.0 RC6

2018-02-06 Thread Felix Schumacher


Am 06.02.2018 08:49, schrieb Philippe Mouawad:

Hi,
Nothing on my side.


Ready, too.

Felix


Regards

On Tuesday, February 6, 2018, Milamber  wrote:



Hello,

I can start the RC7 or you are some new bugs found or fixes to commit?

Milamber

On 05/02/2018 19:15, Milamber wrote:




On 05/02/2018 12:29, sebb wrote:


On 5 February 2018 at 06:28, Milamber  wrote:



On 04/02/2018 20:43, Philippe Mouawad wrote:


Hello,
Following Felix feedback, I rollback my +1 vote.
[-1]   I do not support this release because:

 - I am afraid JMETER_HEAP will disturb users
 - It is not clean that we use 2 different env variables
 - Same that mirror-server is broken
 - The warnings regarding Java 9 should also be dropped or a 
clear

 statement should be in documentation
 - This might introduce issues:
- https://github.com/oblac/jodd/issues/567



OK I will prepare a new RC when we are ready.
Please, continue your tests with the RC6 to try to find other 
blocking

issue
in advance for the RC7 ;)


Would it be possible for next release to reduce the 72 hours or not 
?




The ASF vote page don't indicate the 72h period.


It does state 72 hours:

https://www.apache.org/foundation/voting.html#expressing-
votes-1-0-1-and-fractions



Oops, I was not very awakening this morning ;-)



It's indicate into the lazy consensus.



Not sure what that means.



https://www.apache.org/foundation/glossary.html#LazyConsensus


So (I suppose) if a majority of binding vote come into a small time 
after
the begin of vote period, it's would possible to release more 
quickly...



It may be acceptable for an emergency release, but is not acceptable
for normal releases.



OK. Wait 72h for RC7

Thanks sebb



https://www.apache.org/foundation/voting.html




Regards





On Sun, Feb 4, 2018 at 8:10 PM, Milamber  
wrote:


On 03/02/2018 19:11, Felix Schumacher wrote:


Am 02.02.2018 um 16:33 schrieb Milamber:


Hello,


The sixth (oups) release candidate for JMeter 4.0 (r1822967) 
has

been
prepared, and your votes are solicited.

This release brings a new default theme (Darcula), support for 
Java

9,
74 enhancements (new features and improvements), and 26 bug 
fixes.


Please, test this release candidate (with load tests and/or
functional
tests) using Java 8 or 9 on Linux/Windows/Mac OS, especially on 
the

changes. Feedback is very welcome within the next 72 hours.

You can read the New and Noteworthy section with some 
screenshots to

illustrate improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-4.0RC6/docs/changes.html

JMeter is a Java desktop application designed to load test
functional
behavior and measure performance. The current version targets 
Java

8 /
9.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v4.0_RC6/
(dist revision r24640)

RAT report:

http://home.apache.org/~milamber/jmeter-4.0RC6/dist/rat-
report-jmeter-4.0RC6.txt

MD5 hashes of archives for this vote:

a497d140f1956ba65cf15930b0638333 *apache-jmeter-4.0.tgz
8b7015e303b3aac83d1a050cb3782860 *apache-jmeter-4.0.zip
b3d9cce11b04be574a47b4108a3d2bc6 *apache-jmeter-4.0_src.tgz
04dbd79c242192cdcde574e10c7c43cd *apache-jmeter-4.0_src.zip


Site Docs are here:
http://home.apache.org/~milamber/jmeter-4.0RC6/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapache
jmeter-1027/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v4_0_RC6/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 4.0 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on 
changes

page.
http://home.apache.org/~milamber/jmeter-4.0RC6/docs/changes.
html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[x] +1  I support this release

I found three minor bugs:


   * in bin/mirror-server.*. Those scripts are referring to 
log4j

2.8.2
while we have 2.10.0 in the lib path. The mirror-server will not
start
with
those values.

* the HEAP variables in jmeter.sh and jmeter.bat are named
differently
(and are documented with their correct names), but JMeter prints 
out

to
modify JMETER_HEAP in the batch file. We should probably name 
those

two
variables (HEAP for batch and JMETER_HEAP for shell) the same. 
Apart

from
this the user should not edit the shell scripts, but place those
variables
into bin/setenv.* :)

   * to run  ant test I have to unset the variables LANG and 
LC_*.
Otherwise the tcp tests will fail as there are language 
dependent

error
messages embedded in the csv files that get compared.

You continue with your +1 vote or you prefer apply a -1 vote 
(and go

to a
new RC)?




Regards,

   Felix


[  ] +0  I am OK with this release


[  ] -0   OK, but
[  ] -1   I do not

[VOTE] Release JMeter 4.0 RC7

Re: svn commit: r1823414 - in /jmeter/tags/v4_0_RC7: ./ build.xml

Re: svn commit: r1823414 - in /jmeter/tags/v4_0_RC7: ./ build.xml

Jenkins build is back to normal : JMeter Windows #1012

Jenkins build is back to normal : JMeter-trunk #6657

Build failed in Jenkins: JMeter Ubuntu #405

[GitHub] jmeter pull request #341: Test isIgnore after post processor and assertions

[GitHub] jmeter issue #374: Add a 'go to top' button that gets shown, when page is sc...

Bug 62082: __groovy function seems to have useless synchronized in execute

Re: [VOTE] Release JMeter 4.0 RC6

10 matches

Site Navigation

Mail list logo

Footer information