buildbot success in on jmeter-nightly

2018-07-28 Thread buildbot 
The Buildbot has detected a restored build on builder jmeter-nightly while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-nightly/builds/1112

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 succeeded!

Sincerely,
 -The Buildbot

Re: Release 5.0 ?

2018-07-28 Thread Philippe Mouawad 
On Sat, Jul 28, 2018 at 6:49 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am Samstag, den 28.07.2018, 17:29 +0200 schrieb Philippe Mouawad:
> > Hello,
> >
> > @Felix, I reviewed the PR for the 62463, it looks good to me.
> > We could release with 62570 not fixed as it's an enhancement
>
> The fix for 62463 is only a partial fix. Try to run a distributed load
> test with fixed rmi port in the GUI. You will get exceptions, as the
> (remote) listeners will be instantiated more than one time and try to
> bind to the same fixed port.
>
> I am not sure to understand exactly what the bug is .

I recently ran a NON Gui distributed test and had no issues.
Do it happens with any test plan, only in GUI mode ... ?

It is not clear to me, what we should do with those listeners.
>

Which ones ?

>
> 1) they seem to be intended rather globally, but are local to a thread
> group. I think this is odd, at least
>
> 2) the should probably not be instantiated (cloned?) more than once in
> a test run
>
> What was the original intention for those listeners? Can they be
> implemented as global singleton like objects? If not, how is the other
> side of the remote connection able to distinguish those objects?
>
> For 62570 (enhancement related to validity of CA), I think I would be a
> good idea to add the hint about the property to the dialog that appears
> after the creation of a new CA. All further enhancements on this case
> can wait.
>

yes, ok for me.

>
> Regards,
>  Felix
>
> >
> > Once committed, can we start a release 5.0 ?
> > We haven't released since
> >
> >
> > On Sun, Jul 8, 2018 at 10:44 AM, Philippe Mouawad <
> > philippe.moua...@gmail.com> wrote:
> >
> > > Thanks for feedback.
> > > Usually it’s a good thing to test integrity with sha of the file
> > > and
> > > compare it with the value we advertise.
> > >
> > > Regards
> > >
> > >
> > > On Sunday, July 8, 2018, Jmeter Tea  wrote:
> > >
> > > > I downloaded again and now it's working, maybe I had a problem
> > > > with
> > > > downloading
> > > >
> > > > Thank you
> > > > On Sun, Jul 8, 2018 at 11:35 AM, Philippe Mouawad <
> > > > philippe.moua...@gmail.com> wrote:
> > > >
> > > > > Hello,
> > > > > Which file did you download and from which link ?
> > > > >
> > > > >
> > > > > Thank you
> > > > >
> > > > > On Sunday, July 8, 2018, Jmeter Tea 
> > > > > wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > I download latest nightly r1835292 and it failed to run due
> > > > > > to missing
> > > > > > files in bin folder as
> > > > > > jmeter.properties and log4j2.xml
> > > > > >
> > > > > > FYI
> > > > > >
> > > > > >
> > > > > > On Thu, Jul 5, 2018 at 11:47 PM, Philippe Mouawad <
> > > > > > p.moua...@ubik-ingenierie.com> wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > We have currently 64 bugs/enhancements implemented in trunk
> > > > > > > that
> > > >
> > > > would
> > > > > > > deserve a Major new version 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&
> > > > > > > resolution=FIXED_
> > > > > > >milestone=JMETER_4.1
> > > > > > > > > > > > > status=RESOLVED_status=VERIFIED_status=CLOSED&
> > > > > > > component=HTTP=Main_id=170488=
> > > > > > > Importance=JMeter_format=advanced&
> > > > >
> > > > > resolution=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 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
> > > > > > >

Re: Release 5.0 ?

2018-07-28 Thread Felix Schumacher 
Am Samstag, den 28.07.2018, 17:29 +0200 schrieb Philippe Mouawad:
> Hello,
> 
> @Felix, I reviewed the PR for the 62463, it looks good to me.
> We could release with 62570 not fixed as it's an enhancement

The fix for 62463 is only a partial fix. Try to run a distributed load
test with fixed rmi port in the GUI. You will get exceptions, as the
(remote) listeners will be instantiated more than one time and try to
bind to the same fixed port.

It is not clear to me, what we should do with those listeners.

1) they seem to be intended rather globally, but are local to a thread
group. I think this is odd, at least

2) the should probably not be instantiated (cloned?) more than once in
a test run

What was the original intention for those listeners? Can they be
implemented as global singleton like objects? If not, how is the other
side of the remote connection able to distinguish those objects?

For 62570 (enhancement related to validity of CA), I think I would be a
good idea to add the hint about the property to the dialog that appears
after the creation of a new CA. All further enhancements on this case
can wait.

Regards,
 Felix

> 
> Once committed, can we start a release 5.0 ?
> We haven't released since
> 
> 
> On Sun, Jul 8, 2018 at 10:44 AM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
> 
> > Thanks for feedback.
> > Usually it’s a good thing to test integrity with sha of the file
> > and
> > compare it with the value we advertise.
> > 
> > Regards
> > 
> > 
> > On Sunday, July 8, 2018, Jmeter Tea  wrote:
> > 
> > > I downloaded again and now it's working, maybe I had a problem
> > > with
> > > downloading
> > > 
> > > Thank you
> > > On Sun, Jul 8, 2018 at 11:35 AM, Philippe Mouawad <
> > > philippe.moua...@gmail.com> wrote:
> > > 
> > > > Hello,
> > > > Which file did you download and from which link ?
> > > > 
> > > > 
> > > > Thank you
> > > > 
> > > > On Sunday, July 8, 2018, Jmeter Tea 
> > > > wrote:
> > > > 
> > > > > Hi
> > > > > 
> > > > > I download latest nightly r1835292 and it failed to run due
> > > > > to missing
> > > > > files in bin folder as
> > > > > jmeter.properties and log4j2.xml
> > > > > 
> > > > > FYI
> > > > > 
> > > > > 
> > > > > On Thu, Jul 5, 2018 at 11:47 PM, Philippe Mouawad <
> > > > > p.moua...@ubik-ingenierie.com> wrote:
> > > > > 
> > > > > > Hello,
> > > > > > 
> > > > > > We have currently 64 bugs/enhancements implemented in trunk
> > > > > > that
> > > 
> > > would
> > > > > > deserve a Major new version 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&
> > > > > > resolution=FIXED_
> > > > > >milestone=JMETER_4.1
> > > > > > > > > > > status=RESOLVED_status=VERIFIED_status=CLOSED&
> > > > > > component=HTTP=Main_id=170488=
> > > > > > Importance=JMeter_format=advanced&
> > > > 
> > > > resolution=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 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.
> > > > > > 
> > > > > > -
> > > > > > ---
> > > > > > 
> > > > > > --
> > > > > > Regards.
> > > > > > Philippe  M.
> > > > > > 
> > > > 
> > > > 
> > > > --
> > > > Cordialement.
> > > > Philippe Mouawad.
> > > > 
> > 
> > 
> > --
> > Cordialement.
> > Philippe Mouawad.
> > 
> > 
> > 
> > 
> 
>

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

2018-07-28 Thread Apache Jenkins Server 
See

Re: Release 5.0 ?

2018-07-28 Thread Philippe Mouawad 
Hello,

@Felix, I reviewed the PR for the 62463, it looks good to me.
We could release with 62570 not fixed as it's an enhancement

Once committed, can we start a release 5.0 ?
We haven't released since


On Sun, Jul 8, 2018 at 10:44 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Thanks for feedback.
> Usually it’s a good thing to test integrity with sha of the file and
> compare it with the value we advertise.
>
> Regards
>
>
> On Sunday, July 8, 2018, Jmeter Tea  wrote:
>
>> I downloaded again and now it's working, maybe I had a problem with
>> downloading
>>
>> Thank you
>> On Sun, Jul 8, 2018 at 11:35 AM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>> > Hello,
>> > Which file did you download and from which link ?
>> >
>> >
>> > Thank you
>> >
>> > On Sunday, July 8, 2018, Jmeter Tea  wrote:
>> >
>> > > Hi
>> > >
>> > > I download latest nightly r1835292 and it failed to run due to missing
>> > > files in bin folder as
>> > > jmeter.properties and log4j2.xml
>> > >
>> > > FYI
>> > >
>> > >
>> > > On Thu, Jul 5, 2018 at 11:47 PM, Philippe Mouawad <
>> > > p.moua...@ubik-ingenierie.com> wrote:
>> > >
>> > > > Hello,
>> > > >
>> > > > We have currently 64 bugs/enhancements implemented in trunk that
>> would
>> > > > deserve a Major new version 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&
>> > > > resolution=FIXED_
>> > > >milestone=JMETER_4.1
>> > > >> > > > status=RESOLVED_status=VERIFIED_status=CLOSED&
>> > > > component=HTTP=Main_id=170488=
>> > > > Importance=JMeter_format=advanced&
>> > resolution=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 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.
>> > > >
>> > > > 
>> > > > 
>> > > > --
>> > > > Regards.
>> > > > Philippe  M.
>> > > >
>> > >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>> >
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

buildbot success in on jmeter-trunk

2018-07-28 Thread 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/3886

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] 1836922
Blamelist: pmouawad

Build succeeded!

Sincerely,
 -The Buildbot

Build failed in Jenkins: JMeter-trunk #6858

2018-07-28 Thread Apache Jenkins Server 
See 


Changes:

[pmouawad] Bug 62550 - Modify SubResult Naming Policy
Rename Sample Results generated by Debug Post Processor (by the way a bit 
strange that a Post Processor generates SampleResults ?)
Bugzilla Id: 62550

[pmouawad] Bug 62550 - Modify SubResult Naming Policy

Bugzilla Id: 62550

--
[...truncated 188.41 KB...]
  
  Non-TEXT response data, cannot record: 
()


  

  
  Non-TEXT response data, cannot record: 
()


  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  


  
  


  
  

















  


  Non-TEXT response data, cannot record: 
()


  


  Non-TEXT response data, cannot record: 
()


  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()



  


  Non-TEXT response data, cannot record: 
()











  



  



  



  

  
  Non-TEXT response data, cannot record: 
()


  

  
  Non-TEXT response data, cannot record: 
()


  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  

  
  Non-TEXT response data, cannot record: 
()


  
  


  
  


  
  




Total time: 5 minutes 49 seconds
Build step 'Invoke Ant' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found 
but none of them are new. Did leafNodes run? 
For example, 

 is 12 days old

Build failed in Jenkins: JMeter-trunk #6857

2018-07-28 Thread Apache Jenkins Server 
See 


Changes:

[pmouawad] Bug 62550 - Modify SubResult Naming Policy

Bugzilla Id: 62550

[pmouawad] Cleanup

[pmouawad] Closing invalid PR 390 Update mongo-java-driver version
This closes #390

[pmouawad] Closing invalid PR 393 Jmeter 2.4.x
This closes #393

--
[...truncated 173.02 KB...]
batchtest:
 [echo] Starting TestResultStatusAction with file 
TestResultStatusAction.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/TestResultStatusAction.jmx
   [jmeter] Starting the test @ Sat Jul 28 14:02:56 UTC 2018 (1532786576667)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary =135 in 00:00:01 =  141.2/s Avg: 0 Min: 0 Max:  
  68 Err:18 (13.33%)
   [jmeter] Tidying up ...@ Sat Jul 28 14:02:59 UTC 2018 (1532786579032)
   [jmeter] ... end of run
 [echo] TestResultStatusAction output files compared OK

batchtest:
 [echo] Starting TestRedirectionPolicies with file 
TestRedirectionPolicies.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/TestRedirectionPolicies.jmx
   [jmeter] Starting the test @ Sat Jul 28 14:03:02 UTC 2018 (1532786582445)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary +  1 in 00:00:01 =0.8/s Avg:   297 Min:   297 Max:  
 297 Err: 0 (0.00%) Active: 1 Started: 1 Finished: 0
   [jmeter] summary +  5 in 00:00:01 =5.5/s Avg:   159 Min:75 Max:  
 270 Err: 0 (0.00%) Active: 0 Started: 2 Finished: 2
   [jmeter] summary =  6 in 00:00:02 =2.8/s Avg:   182 Min:75 Max:  
 297 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Sat Jul 28 14:03:05 UTC 2018 (1532786585896)
   [jmeter] ... end of run

BUILD FAILED
:2831: The 
following error occurred while executing this line:
:2795: XML Files 
are not identical.





  
RA_200
false
false
  
  
JSA_0SR
false
false
  
  
RA_Redirected
false
false
  


  
RA_302
false
false
  
  
JSA_0SR
false
false
  


  
RA_200
false
false
  
  
JSA_2SR
false
false
  
  
RA_Redirected
false
false
  
  http://httpbin.org/redirect/1; rc="302" rm="FOUND" 
dt="text"/>
  http://httpbin.org/get; rc="200" rm="OK" dt="text"/>


  
RA_302
false
false
  
  
JSA_0SR
false
false
  


  
RA_200
false
false
  
  
JSA_2SR
false
false
  
  
RA_Redirected
false
false
  
  http://httpbin.org/redirect/1; rc="302" rm="FOUND" 
dt="text"/>
  http://httpbin.org/get; rc="200" rm="OK" dt="text"/>


  
RA_200
false
false
  
  
JSA_0SR
false
false
  
  
RA_Redirected
false
false
  









  
RA_200
false
false
  
  
JSA_0SR
false
false
  
  
RA_Redirected
false
false
  


  
RA_302
false
false
  
  
JSA_0SR
false
false
  


  
RA_200
false
false
  
  
JSA_2SR
false
false
  
  
RA_Redirected
false
false
  
  
  


  
RA_302
false
false
  
  
JSA_0SR
false
false
  


  
RA_200
false
false
  
  
JSA_2SR
false
false
  
  
RA_Redirected
false

[GitHub] jmeter issue #389: Open different RemoteObjects on different ports.

2018-07-28 Thread pmouawad 
Github user pmouawad commented on the issue:

https://github.com/apache/jmeter/pull/389
  
This looks good to me.
Thanks


---

[GitHub] jmeter pull request #390: Update mongo-java-driver version

2018-07-28 Thread asfgit 
Github user asfgit closed the pull request at:

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


---

[GitHub] jmeter pull request #393: Jmeter 2.4.x

2018-07-28 Thread asfgit 
Github user asfgit closed the pull request at:

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


---