You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <ph...@gmail.com> on 2017/02/26 22:10:20 UTC
Re: buildbot failure in on jmeter-trunk
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, <bu...@apache.org> 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
Posted by sebb <se...@gmail.com>.
On 27 February 2017 at 06:37, Philippe Mouawad
<ph...@gmail.com> 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 <se...@gmail.com> wrote:
>
>> On 27 February 2017 at 00:30, sebb <sebbaz@gmail.com <javascript:;>>
>> 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
>> > <philippe.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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, <buildbot@apache.org
>> <javascript:;>> 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
Posted by Philippe Mouawad <ph...@gmail.com>.
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 <se...@gmail.com> wrote:
> On 27 February 2017 at 00:30, sebb <sebbaz@gmail.com <javascript:;>>
> 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
> > <philippe.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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.mouawad@gmail.com <javascript:;>> 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, <buildbot@apache.org
> <javascript:;>> 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
Posted by sebb <se...@gmail.com>.
On 27 February 2017 at 00:30, sebb <se...@gmail.com> 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
> <ph...@gmail.com> 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.mouawad@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.mouawad@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.mouawad@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.mouawad@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, <bu...@apache.org> 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
Posted by sebb <se...@gmail.com>.
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
<ph...@gmail.com> 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.mouawad@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.mouawad@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.mouawad@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.mouawad@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, <bu...@apache.org> 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
Posted by Philippe Mouawad <ph...@gmail.com>.
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.mouawad@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.mouawad@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.mouawad@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.mouawad@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, <bu...@apache.org> 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
Posted by Philippe Mouawad <ph...@gmail.com>.
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.mouawad@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.mouawad@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.mouawad@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, <bu...@apache.org> 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
Posted by Philippe Mouawad <ph...@gmail.com>.
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.mouawad@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.mouawad@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, <bu...@apache.org> 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
Posted by Philippe Mouawad <ph...@gmail.com>.
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.mouawad@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, <bu...@apache.org> 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.