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 frequent
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 fr
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
>
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:
>
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
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/
>
>
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 i
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
> >
> > re
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
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 sett
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 Mouawa
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
>
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-bat
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
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 ha
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'v
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.
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 thin
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 R
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
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/1
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 pr
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
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 failur
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-t
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 derivin
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 part
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 <
fel
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
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]
[
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
31 matches
Mail list logo
