buildbot failure in on jmeter-nightly

[buildbot]

The Buildbot has detected a new failure on builder jmeter-nightly while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-nightly/builds/1091

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave7_ubuntu

Build Reason: The Nightly scheduler named 'jmeterNightly' triggered this build
Build Source Stamp: [branch jmeter/trunk] HEAD
Blamelist: 

BUILD FAILED: failed shell_5

Sincerely,
 -The Buildbot

Build failed in Jenkins: JMeter Windows #1103

[Apache Jenkins Server]

See 


Changes:

[fschumacher] javadoc fixes. Add description to throws tag and really use code 
tag

[fschumacher] Fix usage of ports, when client.rmi.localport is set for 
distributed runs.

This is not a complete fix, as there can be more than one Listener and
they can be initialized more than once. That will lead to exceptions.

Bugzilla Id: 62463

[pmouawad] Make field name clearer

--
[...truncated 192.00 KB...]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPreProcessors(JMeterThread.java:935) 
~[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:537)
 ~[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1835312]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-07-07 15:24:16,766 ERROR o.a.j.t.JMeterThread: Error while 
processing sampler: 'JDBC_With_Failing_PostProcessor'.
   [concat] java.lang.IllegalArgumentException: Variable Name must not be null 
in JDBC PostProcessor
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.AbstractJDBCProcessor.process(AbstractJDBCProcessor.java:45)
 ~[ApacheJMeter_jdbc.jar:r1835312]
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.JDBCPostProcessor.process(JDBCPostProcessor.java:33)
 ~[ApacheJMeter_jdbc.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPostProcessors(JMeterThread.java:925) 
~[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:564)
 ~[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1835312]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1835312]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-07-07 15:24:16,767 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PreProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
   [concat] 2018-07-07 15:24:16,779 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PostProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
 [echo] JDBC_TESTS output files compared OK

batchtest:
 [echo] Starting JMS_TESTS with file JMS_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/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/JMS_TESTS.jmx
   [jmeter] Starting the test @ Sat Jul 07 15:24:20 UTC 2018 (1530977060625)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary +  4 in 00:00:08 =0.5/s Avg:  1105 Min:35 Max:  
3528 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary + 23 in 00:00:32 =0.7/s Avg:   605 Min: 0 Max:  
3038 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary = 27 in 00:00:40 =0.7/s Avg:   679 Min: 0 Max:  
3528 Err: 0 (0.00%)
   [jmeter] summary = 27 in 00:00:40 =0.7/s Avg:   679 Min: 0 Max:  
3528 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Sat Jul 07 15:25:02 UTC 2018 (1530977102668)
   [jmeter] ... end of run
   [concat] 2018-07-07 15:25:02,631 ERROR o.a.j.p.j.c.Publisher: Error during 
close: 
   [concat] javax.jms.JMSException: Cannot send, channel has already failed: 
tcp://127.0.0.1:61616
   [concat] at 
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
 ~[activemq-all-5.15.2.jar:5.15.2]
   [concat] at 
org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1310)
 ~[activemq-all-5.15.2.jar:5.15.2]
   [concat] at 
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1302)
 ~[activemq-all-5.15.2.jar:5.15.2]
   [concat] at 
org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:2075) 
~[activemq-all-5.15.2.jar:5.15.2]
   [concat] at 

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

[Apache Jenkins Server]

See 

Build failed in Jenkins: JMeter-trunk #6834

[Apache Jenkins Server]

See 


Changes:

[fschumacher] Fix usage of ports, when client.rmi.localport is set for 
distributed runs.

This is not a complete fix, as there can be more than one Listener and
they can be initialized more than once. That will lead to exceptions.

Bugzilla Id: 62463

[pmouawad] Make field name clearer

--
[...truncated 193.96 KB...]
 [echo] TEST_HTTPS output files compared OK

batchtest:
 [echo] Starting TestCookieManager with file TestCookieManager.jmx using -X 
-Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:
   [jmeter] SLF4J: Found binding in 
[jar:
   [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/TestCookieManager.jmx
   [jmeter] Starting the test @ Sat Jul 07 14:03:34 UTC 2018 (1530972214054)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary +  1 in 00:00:01 =1.7/s Avg:   556 Min:   556 Max:  
 556 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary +  9 in 00:00:01 =   10.9/s Avg:48 Min: 1 Max:  
 301 Err: 0 (0.00%) Active: 0 Started: 1 Finished: 1
   [jmeter] summary = 10 in 00:00:01 =7.1/s Avg:99 Min: 1 Max:  
 556 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Sat Jul 07 14:03:36 UTC 2018 (1530972216698)
   [jmeter] ... end of run
 [echo] TestCookieManager output files compared OK

batchtest:
 [echo] Starting TCP_TESTS with file TCP_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:
   [jmeter] SLF4J: Found binding in 
[jar:
   [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/TCP_TESTS.jmx
   [jmeter] Starting the test @ Sat Jul 07 14:03:40 UTC 2018 (1530972220637)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] 07/07/2018 14:03:44
   [jmeter] 
   [jmeter] 
   [jmeter] summary = 11 in 00:00:05 =2.1/s Avg:   354 Min: 0 Max:  
1015 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Sat Jul 07 14:03:47 UTC 2018 (1530972227040)
   [jmeter] ... end of run
   [concat] 2018-07-07 14:03:44,966 ERROR o.a.j.p.t.s.TCPSampler: 
   [concat] org.apache.jmeter.protocol.tcp.sampler.ReadException: Error reading 
from server, bytes read: 0
   [concat] at 
org.apache.jmeter.protocol.tcp.sampler.TCPClientImpl.read(TCPClientImpl.java:131)
 ~[ApacheJMeter_tcp.jar:r1835311]
   [concat] at 
org.apache.jmeter.protocol.tcp.sampler.TCPSampler.sample(TCPSampler.java:402) 
[ApacheJMeter_tcp.jar:r1835311]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:622) 
[ApacheJMeter_core.jar:r1835311]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:546)
 [ApacheJMeter_core.jar:r1835311]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1835311]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1835311]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_172]
   [concat] Caused by: java.net.SocketTimeoutException: Read timed out
   [concat] at java.net.SocketInputStream.socketRead0(Native Method) 
~[?:1.8.0_172]
   [concat] at 
java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:1.8.0_172]
   [concat] at java.net.SocketInputStream.read(SocketInputStream.java:171) 
~[?:1.8.0_172]
   [concat] at java.net.SocketInputStream.read(SocketInputStream.java:141) 
~[?:1.8.0_172]
   [concat] at java.net.SocketInputStream.read(SocketInputStream.java:127) 
~[?:1.8.0_172]
   [concat] at 
org.apache.jmeter.protocol.tcp.sampler.TCPClientImpl.read(TCPClientImpl.java:114)
 ~[ApacheJMeter_tcp.jar:r1835311]
   [concat] ... 6 more
   [concat] 2018-07-07 

buildbot success in on jmeter-trunk

[buildbot]

The Buildbot has detected a restored build on builder jmeter-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/3835

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave1_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1835311
Blamelist: fschumacher

Build succeeded!

Sincerely,
 -The Buildbot

buildbot failure in on jmeter-trunk

[buildbot]

The Buildbot has detected a new failure on builder jmeter-trunk while building 
. Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/3834

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave1_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1835310
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot

Build failed in Jenkins: JMeter Windows #1102

[Apache Jenkins Server]

See 


Changes:

[fschumacher] Add a rfc-tag to the site docs

[fschumacher] Markup changes

--
[...truncated 508.46 KB...]
batchtest:
 [echo] Starting JDBC_TESTS with file JDBC_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/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/JDBC_TESTS.jmx
   [jmeter] Starting the test @ Sat Jul 07 13:23:54 UTC 2018 (1530969834434)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary = 21 in 00:00:02 =   10.7/s Avg:29 Min: 0 Max:  
 550 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Sat Jul 07 13:23:57 UTC 2018 (1530969837927)
   [jmeter] ... end of run
   [concat] 2018-07-07 13:23:57,887 ERROR o.a.j.t.JMeterThread: Error while 
processing sampler: 'JDBC_With_Failing_PreProcessor'.
   [concat] java.lang.IllegalArgumentException: Variable Name must not be null 
in JDBC PreProcessor
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.AbstractJDBCProcessor.process(AbstractJDBCProcessor.java:45)
 ~[ApacheJMeter_jdbc.jar:r1835306]
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.JDBCPreProcessor.process(JDBCPreProcessor.java:33)
 ~[ApacheJMeter_jdbc.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPreProcessors(JMeterThread.java:935) 
~[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:537)
 ~[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1835306]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-07-07 13:23:57,905 ERROR o.a.j.t.JMeterThread: Error while 
processing sampler: 'JDBC_With_Failing_PostProcessor'.
   [concat] java.lang.IllegalArgumentException: Variable Name must not be null 
in JDBC PostProcessor
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.AbstractJDBCProcessor.process(AbstractJDBCProcessor.java:45)
 ~[ApacheJMeter_jdbc.jar:r1835306]
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.JDBCPostProcessor.process(JDBCPostProcessor.java:33)
 ~[ApacheJMeter_jdbc.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPostProcessors(JMeterThread.java:925) 
~[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:564)
 ~[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1835306]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1835306]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-07-07 13:23:57,906 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PreProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
   [concat] 2018-07-07 13:23:57,917 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PostProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
 [echo] JDBC_TESTS output files compared OK

batchtest:
 [echo] Starting JMS_TESTS with file JMS_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/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/JMS_TESTS.jmx
   [jmeter] Starting the test @ Sat Jul 07 13:24:00 UTC 2018 (1530969840961)
   [jmeter] Waiting for possible 

Re: Release 5.0 ?

[Felix Schumacher]

Am 07.07.2018 um 12:31 schrieb Philippe Mouawad:

Hi Feiix,

My answers inline below

On Saturday, July 7, 2018, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:



Am 5. Juli 2018 22:47:19 MESZ schrieb Philippe Mouawad <
p.moua...@ubik-ingenierie.com>:

Hello,

We have currently 64 bugs/enhancements implemented in trunk that would
deserve a Major new version 5.0 :

Some people are more inclined to install a dot x release (like 4.1) as
they believe them to be more stable.


On the opposite, lot of people think 4.1 would be minor (bug fix mainly) ,
and lot of blogs said about 3.0 and 4.0 that Jmeter had taken 10 years to
release a major version.

That’s why I think it’s better for « marketing » reason to release a 5.0

But it’s not the only reason.
I believe this version deserves a major number:
- The httpclient new Api migration
- Report : New graph and Custom graphs
- XPath 2
- the flow control improvements which will hopefully ease many use cases
- Search improvements. I’ve been using it and it’s a big usability
improvement for correlation
- recorder enhancement, this really also makes life easier

So I believe this 4.1 version would not be a correct version number as due
to the new features and hc4 api migration it might require a bugfix version
5.1.


But if you feel I am wrong, it’s not a problem to name it 4.1.
i mentionned 5.0 in a tweet and here.
4.1 is mentioned in lot of stackoverflow answers and tweets.

It is just a number :)
I am fine with - almost - any number we use.





But as you already anounced that the next version will be called 5.0, I
guess it will be 5.0.


   - https://bz.apache.org/bugzilla/buglist.cgi?bug_
   status=RESOLVED_status=VERIFIED_status=CLOSED&
   component=HTTP=Main_id=170488=
Importance=JMeter_format=advanced=FIXED_
   milestone=JMETER_4.1


I think last commits deserve a deep review /tests related to :

   - Flow Control Action
   - Result Status Action
   - Iterating Controllers

If nobody finds a bug, the new version 5.0 should be released.

I think we should have a look at the rmi port usage problems with the
listeners.


what is the bug number for it ?
62463 I will add a patch to that entry, but it will probably not be the 
full monty.
I will first look at the offset for the used ports. Second would be to 
hinder the listeners from re-registering.


Regards,
 Felix


Thanks


Regards,
  Felix



I propose to send a mail on user mailing list with following content:

---

-

We'd like to release a new version 5.0 with following enhancements /
bugfixes.
We'd like tests and feedback from users.
If you'd like to help testing, you can download a nightly build
tomorrow:

   - https://ci.apache.org/projects/jmeter/nightlies/

Test particularly:

   - Recording
   - Flow Control Action (old Test Action)
- Result Status Action (break loop, switch to next iteration of current
   loop)
   - While Controller / Loop Controller / Foreach Controller

We'll be waiting for 10 days.

---

-

Re: Release 5.0 ?

[Philippe Mouawad]

Hi Feiix,

My answers inline below

On Saturday, July 7, 2018, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

>
>
> Am 5. Juli 2018 22:47:19 MESZ schrieb Philippe Mouawad <
> p.moua...@ubik-ingenierie.com>:
> >Hello,
> >
> >We have currently 64 bugs/enhancements implemented in trunk that would
> >deserve a Major new version 5.0 :
>
> Some people are more inclined to install a dot x release (like 4.1) as
> they believe them to be more stable.


On the opposite, lot of people think 4.1 would be minor (bug fix mainly) ,
and lot of blogs said about 3.0 and 4.0 that Jmeter had taken 10 years to
release a major version.

That’s why I think it’s better for « marketing » reason to release a 5.0

But it’s not the only reason.
I believe this version deserves a major number:
- The httpclient new Api migration
- Report : New graph and Custom graphs
- XPath 2
- the flow control improvements which will hopefully ease many use cases
- Search improvements. I’ve been using it and it’s a big usability
improvement for correlation
- recorder enhancement, this really also makes life easier

So I believe this 4.1 version would not be a correct version number as due
to the new features and hc4 api migration it might require a bugfix version
5.1.


But if you feel I am wrong, it’s not a problem to name it 4.1.
i mentionned 5.0 in a tweet and here.
4.1 is mentioned in lot of stackoverflow answers and tweets.




> But as you already anounced that the next version will be called 5.0, I
> guess it will be 5.0.
>
> >
> >   - https://bz.apache.org/bugzilla/buglist.cgi?bug_
> >   status=RESOLVED_status=VERIFIED_status=CLOSED&
> >   component=HTTP=Main_id=170488=
> >Importance=JMeter_format=advanced=FIXED_
> >   milestone=JMETER_4.1
> > status=RESOLVED_status=VERIFIED_status=CLOSED&
> component=HTTP=Main_id=170488=
> Importance=JMeter_format=advanced=FIXED_
> milestone=JMETER_4.1>
> >
> >I think last commits deserve a deep review /tests related to :
> >
> >   - Flow Control Action
> >   - Result Status Action
> >   - Iterating Controllers
> >
> >If nobody finds a bug, the new version 5.0 should be released.
>
> I think we should have a look at the rmi port usage problems with the
> listeners.


what is the bug number for it ?

Thanks

>
> Regards,
>  Felix
>
> >
> >
> >I propose to send a mail on user mailing list with following content:
> >
> >---
> -
> >
> >We'd like to release a new version 5.0 with following enhancements /
> >bugfixes.
> >We'd like tests and feedback from users.
> >If you'd like to help testing, you can download a nightly build
> >tomorrow:
> >
> >   - https://ci.apache.org/projects/jmeter/nightlies/
> >
> >Test particularly:
> >
> >   - Recording
> >   - Flow Control Action (old Test Action)
> >- Result Status Action (break loop, switch to next iteration of current
> >   loop)
> >   - While Controller / Loop Controller / Foreach Controller
> >
> >We'll be waiting for 10 days.
> >
> >---
> -
>


-- 
Cordialement.
Philippe Mouawad.

Re: Release 5.0 ?

[Felix Schumacher]

Am 5. Juli 2018 22:47:19 MESZ schrieb Philippe Mouawad 
:
>Hello,
>
>We have currently 64 bugs/enhancements implemented in trunk that would
>deserve a Major new version 5.0 :

Some people are more inclined to install a dot x release (like 4.1) as they 
believe them to be more stable. 

But as you already anounced that the next version will be called 5.0, I guess 
it will be 5.0.

>
>   - https://bz.apache.org/bugzilla/buglist.cgi?bug_
>   status=RESOLVED_status=VERIFIED_status=CLOSED&
>   component=HTTP=Main_id=170488=
>Importance=JMeter_format=advanced=FIXED_
>   milestone=JMETER_4.1
>
>
>I think last commits deserve a deep review /tests related to :
>
>   - Flow Control Action
>   - Result Status Action
>   - Iterating Controllers
>
>If nobody finds a bug, the new version 5.0 should be released.

I think we should have a look at the rmi port usage problems with the listeners.

Regards, 
 Felix 

>
>
>I propose to send a mail on user mailing list with following content:
>
>
>
>We'd like to release a new version 5.0 with following enhancements /
>bugfixes.
>We'd like tests and feedback from users.
>If you'd like to help testing, you can download a nightly build
>tomorrow:
>
>   - https://ci.apache.org/projects/jmeter/nightlies/
>
>Test particularly:
>
>   - Recording
>   - Flow Control Action (old Test Action)
>- Result Status Action (break loop, switch to next iteration of current
>   loop)
>   - While Controller / Loop Controller / Foreach Controller
>
>We'll be waiting for 10 days.
>
>

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

[Apache Jenkins Server]

See 

Jenkins build is back to normal : JMeter Ubuntu #490

[Apache Jenkins Server]

See 

buildbot success in on jmeter-trunk

[buildbot]

The Buildbot has detected a restored build on builder jmeter-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/3831

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave1_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1835297
Blamelist: fschumacher

Build succeeded!

Sincerely,
 -The Buildbot

Build failed in Jenkins: JMeter-trunk #6831

[Apache Jenkins Server]

See 

--
[...truncated 153.24 KB...]
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.mongo...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.sampler...
  [javadoc] Constructing Javadoc information...
  [javadoc] Standard Doclet version 1.8.0_172
  [javadoc] Building tree for all the packages and classes...
  [javadoc] 
:87:
 error: unknown tag: columnsMsgParameters
  [javadoc]  * @deprecated don't use {@columnsMsgParameters} as they are 
not moved when the columns
  [javadoc]  ^
  [javadoc] 
:525:
 warning: no description for @throws
  [javadoc]  * @throws XMLStreamException
  [javadoc]^
  [javadoc] 
:526:
 warning: no description for @throws
  [javadoc]  * @throws FactoryConfigurationError
  [javadoc]^
  [javadoc] Building index for all the packages and classes...
  [javadoc] Building index for all classes...
  [javadoc] Generating 

  [javadoc] 1 error
  [javadoc] 2 warnings

compile-tests:
[javac] Compiling 190 source files to 

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
  [groovyc] Compiling 20 source files to 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 

  [groovyc] 


_test:
 [echo] 
 [echo]gump.run = false
 [echo]java.awt.headless = true
 [echo]test.headless = true
 [echo]user.dir = 

[GitHub] jmeter issue #392: Fixed typo in url encoding documentation

[FSchumacher]

Github user FSchumacher commented on the issue:

https://github.com/apache/jmeter/pull/392
  
Thanks for the report. The correct source of the bug is in 
``xdocs/usermanual/functions.xml``. The docs are generated from those sources.


---

[GitHub] jmeter pull request #392: Fixed typo in url encoding documentation

[asfgit]

Github user asfgit closed the pull request at:

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


---

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

[Apache Jenkins Server]

See