Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hi Felix,

I have no strong opinion, I personally use it in English although I'm
french.

The benefit from this check is that the translation in French is complete.
You could do the same with german.

But the cons, is that I doubt we'll be able to complete the translations,
although we get frequently contributions for such translations, so I think
UI translation is necessary to many people who are not comfortable with
english.

Note that with some current translation tools it is becoming possible to
translate safely, I personally use this german website which I find very
helpful :

   - https://deepl.com


Regards


On Wed, Dec 19, 2018 at 11:08 AM Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am Mittwoch, den 19.12.2018, 10:03 + schrieb build...@apache.org:
> > 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/4084
> >
> Do we still want to fail the builds, when the french translation is not
> complete?
>
> Regards,
>  Felix
>
> > 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] 1849285
> > Blamelist: pmouawad
> >
> > BUILD FAILED: failed shell_3
> >
> > Sincerely,
> >  -The Buildbot
> >
> >
> >
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Felix Schumacher]

Am Mittwoch, den 19.12.2018, 10:03 + schrieb build...@apache.org:
> 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/4084
> 
Do we still want to fail the builds, when the french translation is not
complete?

Regards,
 Felix

> 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] 1849285
> Blamelist: pmouawad
> 
> BUILD FAILED: failed shell_3
> 
> Sincerely,
>  -The Buildbot
> 
> 
> 

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

It looks like the fix for Bug 62238 introduced a regression.

Those Iterating Controller are a real nightmare to maintain.

I'd be happy to have some external look on this.

Regards

On Tue, Jul 3, 2018 at 10:30 PM,  wrote:

> 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/3821
>
> 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] 1835022
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hello,
Just to mention this is not a regression.
It just reveals that test was wrong, now it is fixed it reveals an issue in
test or getUseMultipartForPost().

Initial intention of test was IMU to show that if attachment is wrong, it
should be ignored.



On Thu, Apr 5, 2018 at 6:54 PM,  wrote:

> 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/3695
>
> 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] 1828454
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hello,
Anybody has an idea why we have intermittent failure of
ResponseDecompression.jmx test ?
Looks like the server is failing but why ?:

HR2-DEFLATE,Non HTTP response code: java.io.EOFException,Non HTTP
response message: Unexpected end of ZLIB input stream,Thread Group
1-1,text,false

Regards


On Mon, Jan 22, 2018 at 8:36 PM,  wrote:

> 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/3469
>
> 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] 1821929
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Antonio Gomes Rodrigues]

Hi,

I will fix this failure tomorrow

Antonio

2017-10-10 0:16 GMT+02:00 :

> 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/2985
>
> 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] 1811619
> Blamelist: agomes
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on jmeter-trunk

[sebb]

On 27 February 2017 at 06:37, Philippe Mouawad
 wrote:
> Thanks for finding the issue.

In case of interest, I found it by creating a copy of
jmeter.properties and using that as the first property file
(-pcopy.properties)
(I'd already establised that an empty initial property file did not
help so it was most likely to be a missing initial property.)
It was then just a question of disabling all the properties in
copy.properties until I found the one that was needed.
I disabled the entries in chunks to speed things up (sort of binary chop).

Oh, and to speed up testing, one can use a command like the following:

ant batchtest -Dbatchtest.name=TestHeaderManager
-Dbatchtest.variable=jmeter.httpsampler -Dbatchtest.value=Java

> Shouldn't we set this system property in HTTPJavaImpl directly as it's
> mandatory for Jmeter.

It does not affect all Java HTTP tests, and it may only apply to the
Oracle implementation.

Also it probably needs to be set before the Java HTTP code is loaded,
so it may be too late to do so in HTTPJavaImpl.
Even if it works now, there's no guarantee that the JVM won't be
changed so that the property value is fetched earlier.
I don't think the Javadoc says anything about when the property value
is resolved and/or whether it is cached.

> Thanks
>
> On Monday, February 27, 2017, sebb  wrote:
>
>> On 27 February 2017 at 00:30, sebb >
>> wrote:
>> > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6996110
>> >
>> > requires
>> >
>> > -Dsun.net.http.allowRestrictedHeaders=true
>> >
>> > to be set.
>> >
>> > This is done in system.properties.
>> >
>> > system.properties is enabled in jmeter.properties.
>> >
>> > So there must be some JMeter code that causes the Java HTTP code to
>> > pick up the setting between the initial
>> > -ptestfiles/jmeter-batch.properties and the -qjmeter.properties
>> >
>> > A temporary fix is to add
>> >
>> > system.properties=system.properties
>> >
>> > to
>> >
>> > jmeter-batch.properties
>> >
>> > But ideally the code that wakes up the Java HTTP code should be found
>> > and moved so it occurs later.
>> > Otherwise it may cause other strange behaviour.
>>
>> Actually the problem is that the system.properties value is only
>> checked after loading the initial properties file.
>> The secondary property files are processed later.
>> So the system properties are not processed.
>>
>> The default log level is now WARN, so the initial
>> -ptestfiles/jmeter-batch.properties is no longer needed.
>>
>> >
>> > On 26 February 2017 at 22:42, Philippe Mouawad
>> > > wrote:
>> >> Strangely:
>> >> conn.setRequestProperty(HTTPConstants.HEADER_CONNECTION,
>> >> HTTPConstants.KEEP_ALIVE);
>> >>
>> >> has no effect, calling conn.getRequestProperties() returns an empty map.
>> >> If the other order of options is used , then it is ok.
>> >>
>> >> This is really weird.
>> >>
>> >>
>> >>
>> >> On Sun, Feb 26, 2017 at 11:28 PM, Philippe Mouawad <
>> >> philippe.moua...@gmail.com > wrote:
>> >>
>> >>> With current order of properties (-p / -q) it seems :
>> >>> Connection: keep-alive is missing
>> >>>
>> >>> On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
>> >>> philippe.moua...@gmail.com > wrote:
>> >>>
>>  Shouldn't it be :
>>  -pjmeter.properties
>>  -q /testfiles/jmeter-batch.properties
>> 
>>  instead of
>>  -qjmeter.properties
>>  -p /testfiles/jmeter-batch.properties
>> 
>> 
>> 
>>  On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
>>  philippe.moua...@gmail.com > wrote:
>> 
>> > I've found out that it's due to:
>> > -p /testfiles/jmeter-batch.properties
>> >
>> > On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
>> > philippe.moua...@gmail.com > wrote:
>> >
>> >> Hello,
>> >> If anybody understands this failure I'll be happy to get some help.
>> >>
>> >> When I run test in GUI and NON GuI mode it succeeds and generates
>> the
>> >> correct csv.
>> >> But when ran from ant through batchtest it fails.
>> >>
>> >> Any idea ?
>> >> Regards
>> >> Philippe
>> >>
>> >> On Sun, Feb 26, 2017 at 11:07 PM, > > wrote:
>> >>
>> >>> 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/2407
>> >>>
>> >>> 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] 1784486
>> >>> Blamelist: pmouawad
>> >>>
>> >>> BUILD FAILED: failed shell_3
>> >>>
>> >>> Sincerely,

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Thanks for finding the issue.

Shouldn't we set this system property in HTTPJavaImpl directly as it's
mandatory for Jmeter.

Thanks

On Monday, February 27, 2017, sebb  wrote:

> On 27 February 2017 at 00:30, sebb >
> wrote:
> > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6996110
> >
> > requires
> >
> > -Dsun.net.http.allowRestrictedHeaders=true
> >
> > to be set.
> >
> > This is done in system.properties.
> >
> > system.properties is enabled in jmeter.properties.
> >
> > So there must be some JMeter code that causes the Java HTTP code to
> > pick up the setting between the initial
> > -ptestfiles/jmeter-batch.properties and the -qjmeter.properties
> >
> > A temporary fix is to add
> >
> > system.properties=system.properties
> >
> > to
> >
> > jmeter-batch.properties
> >
> > But ideally the code that wakes up the Java HTTP code should be found
> > and moved so it occurs later.
> > Otherwise it may cause other strange behaviour.
>
> Actually the problem is that the system.properties value is only
> checked after loading the initial properties file.
> The secondary property files are processed later.
> So the system properties are not processed.
>
> The default log level is now WARN, so the initial
> -ptestfiles/jmeter-batch.properties is no longer needed.
>
> >
> > On 26 February 2017 at 22:42, Philippe Mouawad
> > > wrote:
> >> Strangely:
> >> conn.setRequestProperty(HTTPConstants.HEADER_CONNECTION,
> >> HTTPConstants.KEEP_ALIVE);
> >>
> >> has no effect, calling conn.getRequestProperties() returns an empty map.
> >> If the other order of options is used , then it is ok.
> >>
> >> This is really weird.
> >>
> >>
> >>
> >> On Sun, Feb 26, 2017 at 11:28 PM, Philippe Mouawad <
> >> philippe.moua...@gmail.com > wrote:
> >>
> >>> With current order of properties (-p / -q) it seems :
> >>> Connection: keep-alive is missing
> >>>
> >>> On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
> >>> philippe.moua...@gmail.com > wrote:
> >>>
>  Shouldn't it be :
>  -pjmeter.properties
>  -q /testfiles/jmeter-batch.properties
> 
>  instead of
>  -qjmeter.properties
>  -p /testfiles/jmeter-batch.properties
> 
> 
> 
>  On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
>  philippe.moua...@gmail.com > wrote:
> 
> > I've found out that it's due to:
> > -p /testfiles/jmeter-batch.properties
> >
> > On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
> > philippe.moua...@gmail.com > wrote:
> >
> >> Hello,
> >> If anybody understands this failure I'll be happy to get some help.
> >>
> >> When I run test in GUI and NON GuI mode it succeeds and generates
> the
> >> correct csv.
> >> But when ran from ant through batchtest it fails.
> >>
> >> Any idea ?
> >> Regards
> >> Philippe
> >>
> >> On Sun, Feb 26, 2017 at 11:07 PM,  > wrote:
> >>
> >>> 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/2407
> >>>
> >>> 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] 1784486
> >>> Blamelist: pmouawad
> >>>
> >>> BUILD FAILED: failed shell_3
> >>>
> >>> Sincerely,
> >>>  -The Buildbot
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
> >>
> >>
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
> >
> >
> 
> 
>  --
>  Cordialement.
>  Philippe Mouawad.
> 
> 
> 
> >>>
> >>>
> >>> --
> >>> Cordialement.
> >>> Philippe Mouawad.
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[sebb]

On 27 February 2017 at 00:30, sebb  wrote:
> http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6996110
>
> requires
>
> -Dsun.net.http.allowRestrictedHeaders=true
>
> to be set.
>
> This is done in system.properties.
>
> system.properties is enabled in jmeter.properties.
>
> So there must be some JMeter code that causes the Java HTTP code to
> pick up the setting between the initial
> -ptestfiles/jmeter-batch.properties and the -qjmeter.properties
>
> A temporary fix is to add
>
> system.properties=system.properties
>
> to
>
> jmeter-batch.properties
>
> But ideally the code that wakes up the Java HTTP code should be found
> and moved so it occurs later.
> Otherwise it may cause other strange behaviour.

Actually the problem is that the system.properties value is only
checked after loading the initial properties file.
The secondary property files are processed later.
So the system properties are not processed.

The default log level is now WARN, so the initial
-ptestfiles/jmeter-batch.properties is no longer needed.

>
> On 26 February 2017 at 22:42, Philippe Mouawad
>  wrote:
>> Strangely:
>> conn.setRequestProperty(HTTPConstants.HEADER_CONNECTION,
>> HTTPConstants.KEEP_ALIVE);
>>
>> has no effect, calling conn.getRequestProperties() returns an empty map.
>> If the other order of options is used , then it is ok.
>>
>> This is really weird.
>>
>>
>>
>> On Sun, Feb 26, 2017 at 11:28 PM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>>> With current order of properties (-p / -q) it seems :
>>> Connection: keep-alive is missing
>>>
>>> On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
>>> philippe.moua...@gmail.com> wrote:
>>>
 Shouldn't it be :
 -pjmeter.properties
 -q /testfiles/jmeter-batch.properties

 instead of
 -qjmeter.properties
 -p /testfiles/jmeter-batch.properties



 On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
 philippe.moua...@gmail.com> wrote:

> I've found out that it's due to:
> -p /testfiles/jmeter-batch.properties
>
> On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Hello,
>> If anybody understands this failure I'll be happy to get some help.
>>
>> When I run test in GUI and NON GuI mode it succeeds and generates the
>> correct csv.
>> But when ran from ant through batchtest it fails.
>>
>> Any idea ?
>> Regards
>> Philippe
>>
>> On Sun, Feb 26, 2017 at 11:07 PM,  wrote:
>>
>>> 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/2407
>>>
>>> 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] 1784486
>>> Blamelist: pmouawad
>>>
>>> BUILD FAILED: failed shell_3
>>>
>>> Sincerely,
>>>  -The Buildbot
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


 --
 Cordialement.
 Philippe Mouawad.



>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[sebb]

http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6996110

requires

-Dsun.net.http.allowRestrictedHeaders=true

to be set.

This is done in system.properties.

system.properties is enabled in jmeter.properties.

So there must be some JMeter code that causes the Java HTTP code to
pick up the setting between the initial
-ptestfiles/jmeter-batch.properties and the -qjmeter.properties

A temporary fix is to add

system.properties=system.properties

to

jmeter-batch.properties

But ideally the code that wakes up the Java HTTP code should be found
and moved so it occurs later.
Otherwise it may cause other strange behaviour.


On 26 February 2017 at 22:42, Philippe Mouawad
 wrote:
> Strangely:
> conn.setRequestProperty(HTTPConstants.HEADER_CONNECTION,
> HTTPConstants.KEEP_ALIVE);
>
> has no effect, calling conn.getRequestProperties() returns an empty map.
> If the other order of options is used , then it is ok.
>
> This is really weird.
>
>
>
> On Sun, Feb 26, 2017 at 11:28 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> With current order of properties (-p / -q) it seems :
>> Connection: keep-alive is missing
>>
>> On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>>> Shouldn't it be :
>>> -pjmeter.properties
>>> -q /testfiles/jmeter-batch.properties
>>>
>>> instead of
>>> -qjmeter.properties
>>> -p /testfiles/jmeter-batch.properties
>>>
>>>
>>>
>>> On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
>>> philippe.moua...@gmail.com> wrote:
>>>
 I've found out that it's due to:
 -p /testfiles/jmeter-batch.properties

 On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
 philippe.moua...@gmail.com> wrote:

> Hello,
> If anybody understands this failure I'll be happy to get some help.
>
> When I run test in GUI and NON GuI mode it succeeds and generates the
> correct csv.
> But when ran from ant through batchtest it fails.
>
> Any idea ?
> Regards
> Philippe
>
> On Sun, Feb 26, 2017 at 11:07 PM,  wrote:
>
>> 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/2407
>>
>> 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] 1784486
>> Blamelist: pmouawad
>>
>> BUILD FAILED: failed shell_3
>>
>> Sincerely,
>>  -The Buildbot
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


 --
 Cordialement.
 Philippe Mouawad.



>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Strangely:
conn.setRequestProperty(HTTPConstants.HEADER_CONNECTION,
HTTPConstants.KEEP_ALIVE);

has no effect, calling conn.getRequestProperties() returns an empty map.
If the other order of options is used , then it is ok.

This is really weird.



On Sun, Feb 26, 2017 at 11:28 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> With current order of properties (-p / -q) it seems :
> Connection: keep-alive is missing
>
> On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Shouldn't it be :
>> -pjmeter.properties
>> -q /testfiles/jmeter-batch.properties
>>
>> instead of
>> -qjmeter.properties
>> -p /testfiles/jmeter-batch.properties
>>
>>
>>
>> On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>>> I've found out that it's due to:
>>> -p /testfiles/jmeter-batch.properties
>>>
>>> On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
>>> philippe.moua...@gmail.com> wrote:
>>>
 Hello,
 If anybody understands this failure I'll be happy to get some help.

 When I run test in GUI and NON GuI mode it succeeds and generates the
 correct csv.
 But when ran from ant through batchtest it fails.

 Any idea ?
 Regards
 Philippe

 On Sun, Feb 26, 2017 at 11:07 PM,  wrote:

> 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/2407
>
> 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] 1784486
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


 --
 Cordialement.
 Philippe Mouawad.



>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

With current order of properties (-p / -q) it seems :
Connection: keep-alive is missing

On Sun, Feb 26, 2017 at 11:15 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Shouldn't it be :
> -pjmeter.properties
> -q /testfiles/jmeter-batch.properties
>
> instead of
> -qjmeter.properties
> -p /testfiles/jmeter-batch.properties
>
>
>
> On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> I've found out that it's due to:
>> -p /testfiles/jmeter-batch.properties
>>
>> On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>>> Hello,
>>> If anybody understands this failure I'll be happy to get some help.
>>>
>>> When I run test in GUI and NON GuI mode it succeeds and generates the
>>> correct csv.
>>> But when ran from ant through batchtest it fails.
>>>
>>> Any idea ?
>>> Regards
>>> Philippe
>>>
>>> On Sun, Feb 26, 2017 at 11:07 PM,  wrote:
>>>
 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/2407

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

 BUILD FAILED: failed shell_3

 Sincerely,
  -The Buildbot




>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Shouldn't it be :
-pjmeter.properties
-q /testfiles/jmeter-batch.properties

instead of
-qjmeter.properties
-p /testfiles/jmeter-batch.properties



On Sun, Feb 26, 2017 at 11:14 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> I've found out that it's due to:
> -p /testfiles/jmeter-batch.properties
>
> On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Hello,
>> If anybody understands this failure I'll be happy to get some help.
>>
>> When I run test in GUI and NON GuI mode it succeeds and generates the
>> correct csv.
>> But when ran from ant through batchtest it fails.
>>
>> Any idea ?
>> Regards
>> Philippe
>>
>> On Sun, Feb 26, 2017 at 11:07 PM,  wrote:
>>
>>> 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/2407
>>>
>>> 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] 1784486
>>> Blamelist: pmouawad
>>>
>>> BUILD FAILED: failed shell_3
>>>
>>> Sincerely,
>>>  -The Buildbot
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

I've found out that it's due to:
-p /testfiles/jmeter-batch.properties

On Sun, Feb 26, 2017 at 11:10 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Hello,
> If anybody understands this failure I'll be happy to get some help.
>
> When I run test in GUI and NON GuI mode it succeeds and generates the
> correct csv.
> But when ran from ant through batchtest it fails.
>
> Any idea ?
> Regards
> Philippe
>
> On Sun, Feb 26, 2017 at 11:07 PM,  wrote:
>
>> 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/2407
>>
>> 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] 1784486
>> Blamelist: pmouawad
>>
>> BUILD FAILED: failed shell_3
>>
>> Sincerely,
>>  -The Buildbot
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hello,
If anybody understands this failure I'll be happy to get some help.

When I run test in GUI and NON GuI mode it succeeds and generates the
correct csv.
But when ran from ant through batchtest it fails.

Any idea ?
Regards
Philippe

On Sun, Feb 26, 2017 at 11:07 PM,  wrote:

> 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/2407
>
> 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] 1784486
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

[Felix Schumacher]

Am 13. November 2016 17:37:00 MEZ, schrieb Milamber :
>
>
>On 13/11/2016 13:06, sebb wrote:
>> On 13 November 2016 at 12:40, Felix Schumacher
>>  wrote:
>>> Am 13.11.2016 13:34, schrieb Milamber:
 Hello,

 With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter.

 I've open a Infra ticket [1] to have a more recent version of Ant
>for
 the CI buildbot task. (currently I thinks it's Ant 1.8.2)

 Already says, this issue isn't a blocker for the 3.1 RC3. I will
>start
 the release process in few hours.

 Milamber

 For the record (in this mailing list) :
 - original JMeter buildbot request [2]
 - current JMeter buildbot config file [3]
>>>
>>> Hemera as a build slave will be gone by the 30. November. I have
>changed the
>>> slaves to bb_slave1_ubuntu in [3] as suggested by infra. But it
>seems that
>>> changing [3] is not enough.
>> AFAIK, some config changes need to be manually applied.
>> You might need to ask Infra to do so.
>
>
>I've just update the Infra ticket to indicate this.

Great.

Felix

>
>
>
>>
>>> So hopefully your ticket will help.
>>>
>>> Regards,
>>>   Felix
>>>
>>>
 [1] https://issues.apache.org/jira/browse/INFRA-12903
 [2] https://issues.apache.org/jira/browse/INFRA-4025
 [3]


>https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/jmeter.conf



 On 13/11/2016 11:26, Milamber wrote:
>
>
> Root cause :
>
> "The if/unless namespaces are only available since Ant 1.9.1."
> the if/unless namespaces was introduced with Bugzilla 60364
>
>
>
>http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command
> On 13/11/2016 10:23, Milamber wrote:
>>
>>
>> On 13/11/2016 10:04, Philippe Mouawad wrote:
>>> Hi,
>>> Can we upgrade ant on build bot ?
>>
>> I don't know.
>>
>>
>> The error come because the call of
>org.apache.jorphan.test.AllTests in
>> _test task don't have the jacocoagent property (with ant 1.8).
>Currently I
>> try to find a bypass like the test.headless property...
>>
>>> Do you plan the release today ?
>>
>> yes, i would like. But this buildbot error is annoying even if
>not a
>> blocker to build JMeter (if I use a Ant > 1.9)
>>
>> Milamber
>>
>>> Thanks
>>>
>>> On Sunday, November 13, 2016, Milamber 
>wrote:
>>>
 I can reproduce this error with Ant 1.8.4. (works fine with Ant
>1.9.7)



 On 12/11/2016 20:41, Philippe Mouawad wrote:

> Hello,
> I don't know how to fix this issue on buildbox.
> It's not happening on jenkins.
>
> Regards
>
> On Sat, Nov 12, 2016 at 4:23 PM,  wrote:
>
> 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/1621
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: hemera_ubuntu
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-jmeter-commit'
>> triggered this build
>> Build Source Stamp: [branch jmeter/trunk] 1769389
>> Blamelist: pmouawad
>>
>> BUILD FAILED: failed shell_3
>>
>> Sincerely,
>> -The Buildbot
>>
>>
>>
>>
>>
>>
>

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

[sebb]

On 13 November 2016 at 12:40, Felix Schumacher
 wrote:
> Am 13.11.2016 13:34, schrieb Milamber:
>>
>> Hello,
>>
>> With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter.
>>
>> I've open a Infra ticket [1] to have a more recent version of Ant for
>> the CI buildbot task. (currently I thinks it's Ant 1.8.2)
>>
>> Already says, this issue isn't a blocker for the 3.1 RC3. I will start
>> the release process in few hours.
>>
>> Milamber
>>
>> For the record (in this mailing list) :
>> - original JMeter buildbot request [2]
>> - current JMeter buildbot config file [3]
>
>
> Hemera as a build slave will be gone by the 30. November. I have changed the
> slaves to bb_slave1_ubuntu in [3] as suggested by infra. But it seems that
> changing [3] is not enough.

AFAIK, some config changes need to be manually applied.
You might need to ask Infra to do so.

> So hopefully your ticket will help.
>
> Regards,
>  Felix
>
>
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-12903
>> [2] https://issues.apache.org/jira/browse/INFRA-4025
>> [3]
>>
>> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/jmeter.conf
>>
>>
>>
>> On 13/11/2016 11:26, Milamber wrote:
>>>
>>>
>>>
>>> Root cause :
>>>
>>> "The if/unless namespaces are only available since Ant 1.9.1."
>>> the if/unless namespaces was introduced with Bugzilla 60364
>>>
>>>
>>> http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command
>>> On 13/11/2016 10:23, Milamber wrote:



 On 13/11/2016 10:04, Philippe Mouawad wrote:
>
> Hi,
> Can we upgrade ant on build bot ?


 I don't know.


 The error come because the call of org.apache.jorphan.test.AllTests in
 _test task don't have the jacocoagent property (with ant 1.8). Currently I
 try to find a bypass like the test.headless property...

>
> Do you plan the release today ?


 yes, i would like. But this buildbot error is annoying even if not a
 blocker to build JMeter (if I use a Ant > 1.9)

 Milamber

>
> Thanks
>
> On Sunday, November 13, 2016, Milamber  wrote:
>
>> I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)
>>
>>
>>
>> On 12/11/2016 20:41, Philippe Mouawad wrote:
>>
>>> Hello,
>>> I don't know how to fix this issue on buildbox.
>>> It's not happening on jenkins.
>>>
>>> Regards
>>>
>>> On Sat, Nov 12, 2016 at 4:23 PM,  wrote:
>>>
>>> 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/1621

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

 Buildslave for this Build: hemera_ubuntu

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

 BUILD FAILED: failed shell_3

 Sincerely,
-The Buildbot







>>>
>>>
>

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

[Felix Schumacher]

Am 13.11.2016 13:34, schrieb Milamber:

Hello,

With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter.

I've open a Infra ticket [1] to have a more recent version of Ant for
the CI buildbot task. (currently I thinks it's Ant 1.8.2)

Already says, this issue isn't a blocker for the 3.1 RC3. I will start
the release process in few hours.

Milamber

For the record (in this mailing list) :
- original JMeter buildbot request [2]
- current JMeter buildbot config file [3]


Hemera as a build slave will be gone by the 30. November. I have changed 
the slaves to bb_slave1_ubuntu in [3] as suggested by infra. But it 
seems that changing [3] is not enough.


So hopefully your ticket will help.

Regards,
 Felix



[1] https://issues.apache.org/jira/browse/INFRA-12903
[2] https://issues.apache.org/jira/browse/INFRA-4025
[3]
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/jmeter.conf



On 13/11/2016 11:26, Milamber wrote:



Root cause :

"The if/unless namespaces are only available since Ant 1.9.1."
the if/unless namespaces was introduced with Bugzilla 60364

http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command 
On 13/11/2016 10:23, Milamber wrote:



On 13/11/2016 10:04, Philippe Mouawad wrote:

Hi,
Can we upgrade ant on build bot ?


I don't know.


The error come because the call of org.apache.jorphan.test.AllTests 
in _test task don't have the jacocoagent property (with ant 1.8). 
Currently I try to find a bypass like the test.headless property...




Do you plan the release today ?


yes, i would like. But this buildbot error is annoying even if not a 
blocker to build JMeter (if I use a Ant > 1.9)


Milamber



Thanks

On Sunday, November 13, 2016, Milamber  wrote:

I can reproduce this error with Ant 1.8.4. (works fine with Ant 
1.9.7)




On 12/11/2016 20:41, Philippe Mouawad wrote:


Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:

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/1621

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

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-jmeter-commit'

triggered this build
Build Source Stamp: [branch jmeter/trunk] 1769389
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
   -The Buildbot

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

[Milamber]

Hello,

With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter.

I've open a Infra ticket [1] to have a more recent version of Ant for 
the CI buildbot task. (currently I thinks it's Ant 1.8.2)


Already says, this issue isn't a blocker for the 3.1 RC3. I will start 
the release process in few hours.


Milamber

For the record (in this mailing list) :
- original JMeter buildbot request [2]
- current JMeter buildbot config file [3]

[1] https://issues.apache.org/jira/browse/INFRA-12903
[2] https://issues.apache.org/jira/browse/INFRA-4025
[3] 
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/jmeter.conf




On 13/11/2016 11:26, Milamber wrote:



Root cause :

"The if/unless namespaces are only available since Ant 1.9.1."
the if/unless namespaces was introduced with Bugzilla 60364

http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command 




On 13/11/2016 10:23, Milamber wrote:



On 13/11/2016 10:04, Philippe Mouawad wrote:

Hi,
Can we upgrade ant on build bot ?


I don't know.


The error come because the call of org.apache.jorphan.test.AllTests 
in _test task don't have the jacocoagent property (with ant 1.8). 
Currently I try to find a bypass like the test.headless property...




Do you plan the release today ?


yes, i would like. But this buildbot error is annoying even if not a 
blocker to build JMeter (if I use a Ant > 1.9)


Milamber



Thanks

On Sunday, November 13, 2016, Milamber  wrote:


I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)



On 12/11/2016 20:41, Philippe Mouawad wrote:


Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:

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/1621

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

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-jmeter-commit'

triggered this build
Build Source Stamp: [branch jmeter/trunk] 1769389
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
   -The Buildbot

Re: buildbot failure in on jmeter-trunk

[Milamber]

Root cause :

"The if/unless namespaces are only available since Ant 1.9.1."
the if/unless namespaces was introduced with Bugzilla 60364

http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command


On 13/11/2016 10:23, Milamber wrote:



On 13/11/2016 10:04, Philippe Mouawad wrote:

Hi,
Can we upgrade ant on build bot ?


I don't know.


The error come because the call of org.apache.jorphan.test.AllTests in 
_test task don't have the jacocoagent property (with ant 1.8). 
Currently I try to find a bypass like the test.headless property...




Do you plan the release today ?


yes, i would like. But this buildbot error is annoying even if not a 
blocker to build JMeter (if I use a Ant > 1.9)


Milamber



Thanks

On Sunday, November 13, 2016, Milamber  wrote:


I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)



On 12/11/2016 20:41, Philippe Mouawad wrote:


Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:

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/1621

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

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-jmeter-commit'

triggered this build
Build Source Stamp: [branch jmeter/trunk] 1769389
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
   -The Buildbot

Re: buildbot failure in on jmeter-trunk

[Milamber]

On 13/11/2016 10:04, Philippe Mouawad wrote:

Hi,
Can we upgrade ant on build bot ?


I don't know.


The error come because the call of org.apache.jorphan.test.AllTests in 
_test task don't have the jacocoagent property (with ant 1.8). Currently 
I try to find a bypass like the test.headless property...




Do you plan the release today ?


yes, i would like. But this buildbot error is annoying even if not a 
blocker to build JMeter (if I use a Ant > 1.9)


Milamber



Thanks

On Sunday, November 13, 2016, Milamber  wrote:


I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)



On 12/11/2016 20:41, Philippe Mouawad wrote:


Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:

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/1621

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

Buildslave for this Build: hemera_ubuntu

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

BUILD FAILED: failed shell_3

Sincerely,
   -The Buildbot

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hi,
Can we upgrade ant on build bot ?

Do you plan the release today ?

Thanks

On Sunday, November 13, 2016, Milamber  wrote:

>
> I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)
>
>
>
> On 12/11/2016 20:41, Philippe Mouawad wrote:
>
>> Hello,
>> I don't know how to fix this issue on buildbox.
>> It's not happening on jenkins.
>>
>> Regards
>>
>> On Sat, Nov 12, 2016 at 4:23 PM,  wrote:
>>
>> 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/1621
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: hemera_ubuntu
>>>
>>> Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit'
>>> triggered this build
>>> Build Source Stamp: [branch jmeter/trunk] 1769389
>>> Blamelist: pmouawad
>>>
>>> BUILD FAILED: failed shell_3
>>>
>>> Sincerely,
>>>   -The Buildbot
>>>
>>>
>>>
>>>
>>>
>>
>

-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Milamber]

I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7)



On 12/11/2016 20:41, Philippe Mouawad wrote:

Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:


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/1621

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

Buildslave for this Build: hemera_ubuntu

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

BUILD FAILED: failed shell_3

Sincerely,
  -The Buildbot

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hello,
I don't know how to fix this issue on buildbox.
It's not happening on jenkins.

Regards

On Sat, Nov 12, 2016 at 4:23 PM,  wrote:

> 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/1621
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: hemera_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit'
> triggered this build
> Build Source Stamp: [branch jmeter/trunk] 1769389
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Thanks for clarifications

On Sun, Oct 9, 2016 at 12:04 PM, sebb  wrote:

> As has already been mentioned, the purpose of the test is to detect
> accidental changes to the JMX format.
>
> If the change is deliberate, then the test needs to be fixed.
>
> However I think it should be fixed by deriving a new test from the old
> one, and replacing that in the list of tests.
> This is particularly true of the GenTest*.jmx files which were
> auto-generated from the relevant versions.
>
> The build file has a 'generator_jar' target:
>
> ant generator_jar
> Run JMeter Gui
> Add a Thread Group
> Add the Test Generator to the WorkBench
> Run the Test Generator
> Save the JMX
>
>
>
> On 8 October 2016 at 12:34, Philippe Mouawad 
> wrote:
> > Thanks Felix.
> > I am not sure either .
> > I remember we need to create a special jmx file for every version (that
> > changes save configuration ?).
> >
> > Sebb knows how to manage this I think.
> > I think we need to document this somewhere .
> >
> > Regards
> > Philippe
> >
> > On Sat, Oct 8, 2016 at 12:43 PM, Felix Schumacher <
> > felix.schumac...@internetallee.de> wrote:
> >
> >> Am Freitag, den 07.10.2016, 23:26 +0200 schrieb Philippe Mouawad:
> >> > Hi,
> >> > Anybody could guide me on how to fix the issue with:
> >> >
> >> >  [java] Loading file testfiles/GuiTest.jmx and saving it back
> >> > changes its size from 44884 to 44879.
> >> >  [java]
> >> >  [java] Loading file testfiles/GuiTest231.jmx and saving it back
> >> > changes its size from 65545 to 65524.
> >> >  [java]
> >> >  [java] Loading file testfiles/GenTest27.jmx and saving it back
> >> > changes its size from 80101 to 80080.
> >> >  [java]
> >> >  [java] Loading file testfiles/GenTest210.jmx and saving it back
> >> > changes its size from 86563 to 86542.
> >> >  [java]
> >> >  [java] Loading file testfiles/GenTest2_13.jmx and saving it back
> >> > changes its size from 87218 to 87197.
> >> >
> >> > Any existing documentation on this ?
> >>
> >> I think these are used to test backwards compatibility of JMeter. Since
> >> we broke it with this commit, they will have to be adapted (which I
> >> already did).
> >>
> >> I don't know, if it is the right thing to do, either.
> >>
> >> Regards,
> >>  Felix
> >>
> >> >
> >> > Thanks
> >> >
> >> >
> >> >
> >> > On Fri, Oct 7, 2016 at 11:22 PM,  wrote:
> >> >
> >> > >
> >> > > 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/1479
> >> > >
> >> > > Buildbot URL: https://ci.apache.org/
> >> > >
> >> > > Buildslave for this Build: hemera_ubuntu
> >> > >
> >> > > Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-
> >> > > commit'
> >> > > triggered this build
> >> > > Build Source Stamp: [branch jmeter/trunk] 1763837
> >> > > Blamelist: pmouawad
> >> > >
> >> > > BUILD FAILED: failed shell_3
> >> > >
> >> > > Sincerely,
> >> > >  -The Buildbot
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[sebb]

As has already been mentioned, the purpose of the test is to detect
accidental changes to the JMX format.

If the change is deliberate, then the test needs to be fixed.

However I think it should be fixed by deriving a new test from the old
one, and replacing that in the list of tests.
This is particularly true of the GenTest*.jmx files which were
auto-generated from the relevant versions.

The build file has a 'generator_jar' target:

ant generator_jar
Run JMeter Gui
Add a Thread Group
Add the Test Generator to the WorkBench
Run the Test Generator
Save the JMX



On 8 October 2016 at 12:34, Philippe Mouawad  wrote:
> Thanks Felix.
> I am not sure either .
> I remember we need to create a special jmx file for every version (that
> changes save configuration ?).
>
> Sebb knows how to manage this I think.
> I think we need to document this somewhere .
>
> Regards
> Philippe
>
> On Sat, Oct 8, 2016 at 12:43 PM, Felix Schumacher <
> felix.schumac...@internetallee.de> wrote:
>
>> Am Freitag, den 07.10.2016, 23:26 +0200 schrieb Philippe Mouawad:
>> > Hi,
>> > Anybody could guide me on how to fix the issue with:
>> >
>> >  [java] Loading file testfiles/GuiTest.jmx and saving it back
>> > changes its size from 44884 to 44879.
>> >  [java]
>> >  [java] Loading file testfiles/GuiTest231.jmx and saving it back
>> > changes its size from 65545 to 65524.
>> >  [java]
>> >  [java] Loading file testfiles/GenTest27.jmx and saving it back
>> > changes its size from 80101 to 80080.
>> >  [java]
>> >  [java] Loading file testfiles/GenTest210.jmx and saving it back
>> > changes its size from 86563 to 86542.
>> >  [java]
>> >  [java] Loading file testfiles/GenTest2_13.jmx and saving it back
>> > changes its size from 87218 to 87197.
>> >
>> > Any existing documentation on this ?
>>
>> I think these are used to test backwards compatibility of JMeter. Since
>> we broke it with this commit, they will have to be adapted (which I
>> already did).
>>
>> I don't know, if it is the right thing to do, either.
>>
>> Regards,
>>  Felix
>>
>> >
>> > Thanks
>> >
>> >
>> >
>> > On Fri, Oct 7, 2016 at 11:22 PM,  wrote:
>> >
>> > >
>> > > 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/1479
>> > >
>> > > Buildbot URL: https://ci.apache.org/
>> > >
>> > > Buildslave for this Build: hemera_ubuntu
>> > >
>> > > Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-
>> > > commit'
>> > > triggered this build
>> > > Build Source Stamp: [branch jmeter/trunk] 1763837
>> > > Blamelist: pmouawad
>> > >
>> > > BUILD FAILED: failed shell_3
>> > >
>> > > Sincerely,
>> > >  -The Buildbot
>> > >
>> > >
>> > >
>> > >
>> >
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Thanks Felix.
I am not sure either .
I remember we need to create a special jmx file for every version (that
changes save configuration ?).

Sebb knows how to manage this I think.
I think we need to document this somewhere .

Regards
Philippe

On Sat, Oct 8, 2016 at 12:43 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am Freitag, den 07.10.2016, 23:26 +0200 schrieb Philippe Mouawad:
> > Hi,
> > Anybody could guide me on how to fix the issue with:
> >
> >  [java] Loading file testfiles/GuiTest.jmx and saving it back
> > changes its size from 44884 to 44879.
> >  [java]
> >  [java] Loading file testfiles/GuiTest231.jmx and saving it back
> > changes its size from 65545 to 65524.
> >  [java]
> >  [java] Loading file testfiles/GenTest27.jmx and saving it back
> > changes its size from 80101 to 80080.
> >  [java]
> >  [java] Loading file testfiles/GenTest210.jmx and saving it back
> > changes its size from 86563 to 86542.
> >  [java]
> >  [java] Loading file testfiles/GenTest2_13.jmx and saving it back
> > changes its size from 87218 to 87197.
> >
> > Any existing documentation on this ?
>
> I think these are used to test backwards compatibility of JMeter. Since
> we broke it with this commit, they will have to be adapted (which I
> already did).
>
> I don't know, if it is the right thing to do, either.
>
> Regards,
>  Felix
>
> >
> > Thanks
> >
> >
> >
> > On Fri, Oct 7, 2016 at 11:22 PM,  wrote:
> >
> > >
> > > 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/1479
> > >
> > > Buildbot URL: https://ci.apache.org/
> > >
> > > Buildslave for this Build: hemera_ubuntu
> > >
> > > Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-
> > > commit'
> > > triggered this build
> > > Build Source Stamp: [branch jmeter/trunk] 1763837
> > > Blamelist: pmouawad
> > >
> > > BUILD FAILED: failed shell_3
> > >
> > > Sincerely,
> > >  -The Buildbot
> > >
> > >
> > >
> > >
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Felix Schumacher]

Am Freitag, den 07.10.2016, 23:26 +0200 schrieb Philippe Mouawad:
> Hi,
> Anybody could guide me on how to fix the issue with:
> 
>  [java] Loading file testfiles/GuiTest.jmx and saving it back
> changes its size from 44884 to 44879.
>  [java]
>  [java] Loading file testfiles/GuiTest231.jmx and saving it back
> changes its size from 65545 to 65524.
>  [java]
>  [java] Loading file testfiles/GenTest27.jmx and saving it back
> changes its size from 80101 to 80080.
>  [java]
>  [java] Loading file testfiles/GenTest210.jmx and saving it back
> changes its size from 86563 to 86542.
>  [java]
>  [java] Loading file testfiles/GenTest2_13.jmx and saving it back
> changes its size from 87218 to 87197.
> 
> Any existing documentation on this ?

I think these are used to test backwards compatibility of JMeter. Since
we broke it with this commit, they will have to be adapted (which I
already did).

I don't know, if it is the right thing to do, either.

Regards,
 Felix

> 
> Thanks
> 
> 
> 
> On Fri, Oct 7, 2016 at 11:22 PM,  wrote:
> 
> > 
> > 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/1479
> > 
> > Buildbot URL: https://ci.apache.org/
> > 
> > Buildslave for this Build: hemera_ubuntu
> > 
> > Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-
> > commit'
> > triggered this build
> > Build Source Stamp: [branch jmeter/trunk] 1763837
> > Blamelist: pmouawad
> > 
> > BUILD FAILED: failed shell_3
> > 
> > Sincerely,
> >  -The Buildbot
> > 
> > 
> > 
> > 
> 

Re: buildbot failure in on jmeter-trunk

[Philippe Mouawad]

Hi,
Anybody could guide me on how to fix the issue with:

 [java] Loading file testfiles/GuiTest.jmx and saving it back
changes its size from 44884 to 44879.
 [java]
 [java] Loading file testfiles/GuiTest231.jmx and saving it back
changes its size from 65545 to 65524.
 [java]
 [java] Loading file testfiles/GenTest27.jmx and saving it back
changes its size from 80101 to 80080.
 [java]
 [java] Loading file testfiles/GenTest210.jmx and saving it back
changes its size from 86563 to 86542.
 [java]
 [java] Loading file testfiles/GenTest2_13.jmx and saving it back
changes its size from 87218 to 87197.

Any existing documentation on this ?

Thanks



On Fri, Oct 7, 2016 at 11:22 PM,  wrote:

> 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/1479
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: hemera_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit'
> triggered this build
> Build Source Stamp: [branch jmeter/trunk] 1763837
> Blamelist: pmouawad
>
> BUILD FAILED: failed shell_3
>
> Sincerely,
>  -The Buildbot
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: buildbot failure in on jmeter-trunk

[Felix Schumacher]

Now that the homepage images changed, we have to change the test with the image 
references.

I will do so in a minute. 

Felix

Am 19. Mai 2016 19:26:04 MESZ, schrieb build...@apache.org:
>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/1181
>
>Buildbot URL: https://ci.apache.org/
>
>Buildslave for this Build: hemera_ubuntu
>
>Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit'
>triggered this build
>Build Source Stamp: [branch jmeter/trunk] 1744608
>Blamelist: fschumacher
>
>BUILD FAILED: failed shell_3
>
>Sincerely,
> -The Buildbot