Re: Drop Commons-HttpClient 3.1

On 14/02/2017 20:57, Philippe Mouawad wrote: On Tue, Feb 14, 2017 at 9:49 PM, Milamber wrote: IMHO, wait 72h to have some feedback or (if no feedback: a lazy consensus) seems good (72h is the traditional delay is ASF) For me it's not an official vote, so the 72 h is

Hello:)

Good Evening! I want to help with translations, can I ask you for the files I need to start with? If that's matter - I'm from Poland. greetings, Bartosz

buildbot success in on jmeter-trunk

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/2224 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

Re: Drop Commons-HttpClient 3.1

On Tue, Feb 14, 2017 at 9:49 PM, Milamber wrote: > > IMHO, wait 72h to have some feedback or (if no feedback: a lazy consensus) > seems good (72h is the traditional delay is ASF) > For me it's not an official vote, so the 72 h is not necessary right ? although we've waited

buildbot failure in on jmeter-trunk

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/2223 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

Re: Drop Commons-HttpClient 3.1

IMHO, wait 72h to have some feedback or (if no feedback: a lazy consensus) seems good (72h is the traditional delay is ASF) For my opinion about the removing the HC 3.1: yes and no... The HC4 (in default config) don't react like HC3.1 (for me), I need to set up this props to my load tests:

[GitHub] jmeter pull request #275: Bug 60664 : Adding log level setting menu under Op...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/275 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

buildbot success in on jmeter-trunk

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/ Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

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

See

Re: Drop Commons-HttpClient 3.1

Hi, I'll wait another 24h. Feedback welcome Regards On Mon, Feb 13, 2017 at 9:05 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > Unless there is NOGO on this, I'll be committing the patch provided > tomorrow on issue: > >-

Build failed in Jenkins: JMeter-trunk #5846

See Changes: [pmouawad] Fix broken MC reference -- [...truncated 1284 lines...] Java 1 C1=2,200,OK,Thread Group 1-1,text,true,,10,1,1,null,,1,0 Loop5 C1=2 C2=1 C3=6,200,OK,Thread Group

buildbot failure in on jmeter-trunk

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/2219 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

Build failed in Jenkins: JMeter-trunk #5845

See Changes: [pmouawad] Try to fix buildbot failure in on jmeter-nightly -- [...truncated 1017 lines...] [anakia] Output:

Re: buildbot failure in on jmeter-nightly

On 14 February 2017 at 07:39, Philippe Mouawad wrote: > Hi Rainer, > Is this a bug or due to agent being overloaded , as I read in comments of > first Thread Group: > "N.B. The ramp-up period is set so that the first thread will finish before > the second. > This is to