CSS Errors and release of ph-css 4.1.6

[Philippe Mouawad]

Hello,
Ph CSS project has released a maintenance version:
https://github.com/phax/ph-css/releases/tag/ph-css-parent-pom-4.1.6

It might be interesting to plug a custom ICSSInterpretErrorHandler in our
case.

I won't be able to work on this before milamber's expected release date so
if anybody can ...

Regards
Philippe

Build failed in Jenkins: JMeter-trunk #5511

[Apache Jenkins Server]

See 

Changes:

[fschumacher] Correct typo.

--
[...truncated 1129 lines...]
[javac] Note: Recompile with -Xlint:deprecation for details.

_test:
 [echo] 
 [echo]gump.run = false
 [echo]java.awt.headless = true
 [echo]test.headless = true
 [echo]user.dir = 
 [echo]basedir = 
 [echo]test dir = build/test
 [echo]test dir gump = build/test
 [echo]testsaveservice.saveout = ${testsaveservice.saveout}
 [echo]test.encoding = UTF-8
 [echo] 
 [java] Setting JMeterHome: 

 [java] Setting up logging props using file: 

 [java] Writing log file to: 

 [java] Using initializeProperties() from org.apache.jmeter.util.JMeterUtils
 [java] Setting up initial properties using: 

 [java] Initializing Properties: 

 [java] Writing log file to: 

 [java] JMeterVersion=r1766108
 [java] java.version=1.7.0_80
 [java] java.home=/usr/local/asfpackages/java/jdk1.7.0_80/jre
 [java] file.encoding=UTF-8
 [java] default encoding=UTF-8
 [java] user.dir=
 [java] Locale=en_US
 [java] os.name=Linux
 [java] os.version=3.13.0-98-generic
 [java] JCE max key length = 128
 [java] +++
 [java] java.awt.headless=true
 [java] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
 [java] 
 [java] Searching junit tests in : build/test
 [java] o.a.j.junit.JMeterTest INFO: JMeterGUIComponent: skipping some 
tests org.apache.jmeter.testbeans.gui.TestBeanGUI
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.config.gui.RowDetailDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.functions.gui.FunctionHelper java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.MainFrame java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.SavePropertyDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.action.SearchTreeDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.action.SelectTemplatesDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.util.EscapeDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.util.JSyntaxTextArea java.awt.HeadlessException
 [java] 

Re: Build failed in Jenkins: JMeter-trunk #5510

[Felix Schumacher]

Am 21.10.2016 um 21:02 schrieb Apache Jenkins Server:

See 

Changes:

...

BUILD FAILED
:2697: The 
following error occurred while executing this line:
:2605: CSV Files 
are not identical.
 

 
label,responseCode,responseMessage,threadName,dataType,success,grpThreads,allThreads,SampleCount,ErrorCount
HTTPS-SNI,200,OK,Thread Group 1-1,text,true,1,1,1,0
HTTPS-Request,200,OK,Thread Group 1-1,text,true,1,1,1,0

 

 
label,responseCode,responseMessage,threadName,dataType,success,grpThreads,allThreads,SampleCount,ErrorCount
HTTPS-SNI,Non HTTP response code: java.net.UnknownHostException,Non HTTP 
response message: sni.velox.ch: Name or service not known,Thread Group 
1-1,text,false,1,1,1,1
HTTPS-Request,200,OK,Thread Group 1-1,text,true,1,1,1,0
I believe this failure has nothing to do with my last changes and could 
be seen first on travisci with our github repo tests.


Any ideas how to fix this?

Regards,
 Felix



Total time: 4 minutes 31 seconds
Build step 'Invoke Ant' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts

Build failed in Jenkins: JMeter-trunk #5510

[Apache Jenkins Server]

See 

Changes:

[fschumacher] JSON Extractor doesn't index array elements when only one element 
is found.
Based on patch by Roberto Braga (roberto.braga at sociale.it).

Bugzilla Id: 60295

--
[...truncated 1188 lines...]
 [echo]java.awt.headless = true
 [echo]test.headless = true
 [echo]user.dir = 
 [echo]basedir = 
 [echo]test dir = build/test
 [echo]test dir gump = build/test
 [echo]testsaveservice.saveout = ${testsaveservice.saveout}
 [echo]test.encoding = UTF-8
 [echo] 
 [java] Setting JMeterHome: 

 [java] Setting up logging props using file: 

 [java] Writing log file to: 

 [java] Using initializeProperties() from org.apache.jmeter.util.JMeterUtils
 [java] Setting up initial properties using: 

 [java] Initializing Properties: 

 [java] Writing log file to: 

 [java] JMeterVersion=r1766100
 [java] java.version=1.7.0_80
 [java] java.home=/usr/local/asfpackages/java/jdk1.7.0_80/jre
 [java] file.encoding=UTF-8
 [java] default encoding=UTF-8
 [java] user.dir=
 [java] Locale=en_US
 [java] os.name=Linux
 [java] os.version=3.19.0-25-generic
 [java] JCE max key length = 128
 [java] +++
 [java] java.awt.headless=true
 [java] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
 [java] 
 [java] Searching junit tests in : build/test
 [java] o.a.j.junit.JMeterTest INFO: JMeterGUIComponent: skipping some 
tests org.apache.jmeter.testbeans.gui.TestBeanGUI
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.config.gui.RowDetailDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.functions.gui.FunctionHelper java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.MainFrame java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.SavePropertyDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.action.SearchTreeDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.action.SelectTemplatesDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.util.EscapeDialog java.awt.HeadlessException
 [java] o.a.j.junit.JMeterTest Error creating 
org.apache.jmeter.gui.util.JSyntaxTextArea java.awt.HeadlessException
 [java] 

buildbot failure in on jmeter-trunk

[buildbot]

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

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] 1766100
Blamelist: fschumacher

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[vlsi]

Github user vlsi commented on the issue:

https://github.com/apache/jmeter/pull/231
  
>In my test plan I have 3 http request and one Exponential Timer at the 
same level

That does not work like this.
Please wrap "expenential timer" into some sampler (e.g. debug action or 
whatever).

In JMeter all timers/listeners are inherited by sibling elements, thus when 
you place a timer at the same level as "3 http requests", you basically invoke 
the timer for each of the page, and that is something odd.

You should have the plan as follows:
```
DebugSampler
   ExpTimer
http1
http2
http3
```


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[ra0077]

Github user ra0077 commented on the issue:

https://github.com/apache/jmeter/pull/231
  
Hi,

In my test plan I have 3 http request and one Exponential Timer at the same 
level

When I run my script, only first http request are executed whereas with 
"Constant Throughput Timer", I don't have this problem


![poisson01](https://cloud.githubusercontent.com/assets/16882234/19597506/546a6a9e-9795-11e6-80ee-d037c2f67463.png)


![poisson02](https://cloud.githubusercontent.com/assets/16882234/19597541/81b8c388-9795-11e6-8950-85fc631f77a4.png)


![poisson03](https://cloud.githubusercontent.com/assets/16882234/19597546/85c9ee84-9795-11e6-80a7-4cb2e6ee169d.png)

Antonio




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[vlsi]

Github user vlsi commented on the issue:

https://github.com/apache/jmeter/pull/231
  
>I have some strange behavior in some test

What is the behavior?

Don't get me wrong, but I think the UI should be obvious. If the UI is 
obscure and/or the tooltip does not help, then it is a good point to update the 
UI.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[ra0077]

Github user ra0077 commented on the issue:

https://github.com/apache/jmeter/pull/231
  
Yes I have read it but I have some strange behavior in some test
It's why I would like to know how do you use it

Antonio


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[vlsi]

Github user vlsi commented on the issue:

https://github.com/apache/jmeter/pull/231
  
@ra0077 , have you seen the tooltips for the input values of the timer?

I'm sure those should explain all the things.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Start the next release 3.1 into 1-2 weeks?

[Antonio Gomes Rodrigues]

Great :-)

Antonio

2016-10-21 11:54 GMT+02:00 Milamber :

>
> I can start the RC1 the 30 oct. or 31 oct as RM.
>
> In waiting, we can start to add some New and Noteworthy screenshots even
> if the 3.1 release is small improvement release.
>
>
>
> On 21/10/2016 09:16, Antonio Gomes Rodrigues wrote:
>
>> Hi,
>>
>> Thank to the answer
>>
>> On my side, it's ok too
>>
>> Antonio
>>
>> 2016-10-20 22:42 GMT+02:00 Philippe Mouawad :
>>
>> Hello,
>>> On my side, I consider work finished for this version.
>>> AFAIK there are 2 pending issues:
>>>
>>> - JSON : Felix has a patch
>>> - Issue reported yesterday by milamber : A rapid fix can be to
>>> increase
>>> precision (not blocker as here since 2.13)
>>>
>>>
>>> Regards
>>> Philippe
>>>
>>> On Thu, Oct 20, 2016 at 11:12 AM, Antonio Gomes Rodrigues <
>>> ra0...@gmail.com>
>>> wrote:
>>>
>>> Hi,

 The release of 3.1 is it still planned?

 Antonio

 2016-10-07 19:42 GMT+02:00 Philippe Mouawad  felix.schumac...@internetallee.de> wrote:
>
> Am 07.10.2016 um 19:29 schrieb Philippe Mouawad:
>>
>> Hello,
>>> Meanwhile jodd manager gave me some feedback, next release will only
>>> support Java 8.
>>>
>>> So we can either decide to migrate to Java8 (only building), I can
>>>
>> this

> way
>>> include the new Browser feature and this new version.
>>> Or we stick to Java 7 hoping that next 3.2 is not too far which I am
>>> afraid
>>> will not be the case.
>>>
>>> I am still in favour of staying on java 7 for this release and hoping
>>
> for

> a short period till the next release.
>>
>> I think we can live with the poor(er) performance of jodd.
>>
>> I wanted to introduce the new Browser faster also.
> But Ok let's stick to Java 7 :-)
>
> Regards,
>>   Felix
>>
>>
>> Regards
>>> Philippe
>>>
>>> On Mon, Oct 3, 2016 at 10:49 AM, Antonio Gomes Rodrigues <
>>> ra0...@gmail.com>
>>> wrote:
>>>
>>> +1
>>>
 Antonio

 2016-10-02 21:33 GMT+02:00 Philippe Mouawad <

>>> philippe.moua...@gmail.com
>
>> :
>
 Hello

> Work on my side is finished for 3.1 upcoming release.
> Except for jsoup and jodd upgrade but as we have no real
>
 visibility
>>>
 on

> release we might decide to proceed with 3.1 release process.
>
> Regards
> Philippe
>
> On Wed, Sep 28, 2016 at 1:48 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>
> On Wed, Sep 28, 2016 at 11:25 AM, Antonio Gomes Rodrigues <
>> ra0...@gmail.com> wrote:
>>
>> Hi,
>>
>>> 2016-09-27 23:43 GMT+02:00 Philippe Mouawad <
>>>
>>> philippe.moua...@gmail.com
>>
> :
>
>> Hello,
>>>
 I would like if possible to integrate the new release of jodd

>>> which

> contains an important performance improvement. It is supposed

>>> to
>>>
 be

> released in few days.

 Do you know when?

>>> No, he said last week it would happen in 2 weeks.
>>>
>> Have you got a link which explain the performance improvement?
>>
>>> https://github.com/oblac/jodd/issues/328
>>>
>> https://github.com/oblac/jodd/issues/327
>> https://github.com/oblac/jodd/issues/329
>> https://github.com/oblac/jodd/pull/330
>> https://github.com/oblac/jodd/issues/331
>> https://github.com/oblac/jodd/pull/332
>>
>>
>>
>> On my side I would like if possible to fix:
>>>
 https://bz.apache.org/bugzilla/show_bug.cgi?id=60015

 +1 to wait to the fix
>>>
>>> It may not be simple.
>>>
>>
>> I have asked a question on dev mailing list.

 I have seen your mail but I don't see question

>>> I was waiting for remarks on analysis.
>>>
>> I may not have the whole picture.
>>
>>
>> But if too complex we can wait for 3.2
>>>
 Regards



 On Tue, Sep 27, 2016 at 11:40 PM, Milamber <

>>> milam...@apache.org>
>>>
 wrote:
>>>
>> Hello,
>>
>>> Ready? I can start the RC1 the 2nd October?
>
> Are you ok?
>
> Milamber
>
>
> On 13/09/2016 15:20, Milamber wrote:
>

Re: Start the next release 3.1 into 1-2 weeks?

[Milamber]

I can start the RC1 the 30 oct. or 31 oct as RM.

In waiting, we can start to add some New and Noteworthy screenshots even 
if the 3.1 release is small improvement release.



On 21/10/2016 09:16, Antonio Gomes Rodrigues wrote:

Hi,

Thank to the answer

On my side, it's ok too

Antonio

2016-10-20 22:42 GMT+02:00 Philippe Mouawad :


Hello,
On my side, I consider work finished for this version.
AFAIK there are 2 pending issues:

- JSON : Felix has a patch
- Issue reported yesterday by milamber : A rapid fix can be to increase
precision (not blocker as here since 2.13)


Regards
Philippe

On Thu, Oct 20, 2016 at 11:12 AM, Antonio Gomes Rodrigues <
ra0...@gmail.com>
wrote:


Hi,

The release of 3.1 is it still planned?

Antonio

2016-10-07 19:42 GMT+02:00 Philippe Mouawad  wrote:


Am 07.10.2016 um 19:29 schrieb Philippe Mouawad:


Hello,
Meanwhile jodd manager gave me some feedback, next release will only
support Java 8.

So we can either decide to migrate to Java8 (only building), I can

this

way
include the new Browser feature and this new version.
Or we stick to Java 7 hoping that next 3.2 is not too far which I am
afraid
will not be the case.


I am still in favour of staying on java 7 for this release and hoping

for

a short period till the next release.

I think we can live with the poor(er) performance of jodd.


I wanted to introduce the new Browser faster also.
But Ok let's stick to Java 7 :-)


Regards,
  Felix



Regards
Philippe

On Mon, Oct 3, 2016 at 10:49 AM, Antonio Gomes Rodrigues <
ra0...@gmail.com>
wrote:

+1

Antonio

2016-10-02 21:33 GMT+02:00 Philippe Mouawad <

philippe.moua...@gmail.com

:

Hello

Work on my side is finished for 3.1 upcoming release.
Except for jsoup and jodd upgrade but as we have no real

visibility

on

release we might decide to proceed with 3.1 release process.

Regards
Philippe

On Wed, Sep 28, 2016 at 1:48 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:



On Wed, Sep 28, 2016 at 11:25 AM, Antonio Gomes Rodrigues <
ra0...@gmail.com> wrote:

Hi,

2016-09-27 23:43 GMT+02:00 Philippe Mouawad <


philippe.moua...@gmail.com

:

Hello,

I would like if possible to integrate the new release of jodd

which

contains an important performance improvement. It is supposed

to

be

released in few days.

Do you know when?

No, he said last week it would happen in 2 weeks.

Have you got a link which explain the performance improvement?

https://github.com/oblac/jodd/issues/328

https://github.com/oblac/jodd/issues/327
https://github.com/oblac/jodd/issues/329
https://github.com/oblac/jodd/pull/330
https://github.com/oblac/jodd/issues/331
https://github.com/oblac/jodd/pull/332




On my side I would like if possible to fix:

https://bz.apache.org/bugzilla/show_bug.cgi?id=60015


+1 to wait to the fix

It may not be simple.



I have asked a question on dev mailing list.

I have seen your mail but I don't see question

I was waiting for remarks on analysis.

I may not have the whole picture.



But if too complex we can wait for 3.2

Regards



On Tue, Sep 27, 2016 at 11:40 PM, Milamber <

milam...@apache.org>

wrote:

Hello,

Ready? I can start the RC1 the 2nd October?

Are you ok?

Milamber


On 13/09/2016 15:20, Milamber wrote:

Hello,

Are you willing to start the next release process withing 1

to

2

weeks?

I


can act as RM.

The next release will keep the Java 7 support (probably this


release

will

be the last with Java 7 support).

What are the bugs which will must be fixed before the next


release?

If you want add an improvement before the next release, please

indicate

now.

Milamber




--
Cordialement.
Philippe Mouawad.



--
Cordialement.
Philippe Mouawad.





--
Cordialement.
Philippe Mouawad.






--
Cordialement.
Philippe Mouawad.




--
Cordialement.
Philippe Mouawad.

Re: Start the next release 3.1 into 1-2 weeks?

[Antonio Gomes Rodrigues]

Hi,

Thank to the answer

On my side, it's ok too

Antonio

2016-10-20 22:42 GMT+02:00 Philippe Mouawad :

> Hello,
> On my side, I consider work finished for this version.
> AFAIK there are 2 pending issues:
>
>- JSON : Felix has a patch
>- Issue reported yesterday by milamber : A rapid fix can be to increase
>precision (not blocker as here since 2.13)
>
>
> Regards
> Philippe
>
> On Thu, Oct 20, 2016 at 11:12 AM, Antonio Gomes Rodrigues <
> ra0...@gmail.com>
> wrote:
>
> > Hi,
> >
> > The release of 3.1 is it still planned?
> >
> > Antonio
> >
> > 2016-10-07 19:42 GMT+02:00 Philippe Mouawad  >:
> >
> > > On Fri, Oct 7, 2016 at 7:40 PM, Felix Schumacher <
> > > felix.schumac...@internetallee.de> wrote:
> > >
> > > > Am 07.10.2016 um 19:29 schrieb Philippe Mouawad:
> > > >
> > > >> Hello,
> > > >> Meanwhile jodd manager gave me some feedback, next release will only
> > > >> support Java 8.
> > > >>
> > > >> So we can either decide to migrate to Java8 (only building), I can
> > this
> > > >> way
> > > >> include the new Browser feature and this new version.
> > > >> Or we stick to Java 7 hoping that next 3.2 is not too far which I am
> > > >> afraid
> > > >> will not be the case.
> > > >>
> > > > I am still in favour of staying on java 7 for this release and hoping
> > for
> > > > a short period till the next release.
> > > >
> > > > I think we can live with the poor(er) performance of jodd.
> > > >
> > >
> > > I wanted to introduce the new Browser faster also.
> > > But Ok let's stick to Java 7 :-)
> > >
> > > >
> > > > Regards,
> > > >  Felix
> > > >
> > > >
> > > >>
> > > >> Regards
> > > >> Philippe
> > > >>
> > > >> On Mon, Oct 3, 2016 at 10:49 AM, Antonio Gomes Rodrigues <
> > > >> ra0...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> +1
> > > >>>
> > > >>> Antonio
> > > >>>
> > > >>> 2016-10-02 21:33 GMT+02:00 Philippe Mouawad <
> > > philippe.moua...@gmail.com
> > > >>> >:
> > > >>>
> > > >>> Hello
> > >  Work on my side is finished for 3.1 upcoming release.
> > >  Except for jsoup and jodd upgrade but as we have no real
> visibility
> > on
> > >  release we might decide to proceed with 3.1 release process.
> > > 
> > >  Regards
> > >  Philippe
> > > 
> > >  On Wed, Sep 28, 2016 at 1:48 PM, Philippe Mouawad <
> > >  philippe.moua...@gmail.com> wrote:
> > > 
> > > 
> > > > On Wed, Sep 28, 2016 at 11:25 AM, Antonio Gomes Rodrigues <
> > > > ra0...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >>
> > > >> 2016-09-27 23:43 GMT+02:00 Philippe Mouawad <
> > > >>
> > > > philippe.moua...@gmail.com
> > > >>>
> > >  :
> > > >
> > > >> Hello,
> > > >>> I would like if possible to integrate the new release of jodd
> > which
> > > >>> contains an important performance improvement. It is supposed
> to
> > be
> > > >>> released in few days.
> > > >>>
> > > >>> Do you know when?
> > > >>
> > > >> No, he said last week it would happen in 2 weeks.
> > > >
> > > > Have you got a link which explain the performance improvement?
> > > >>
> > > >> https://github.com/oblac/jodd/issues/328
> > > > https://github.com/oblac/jodd/issues/327
> > > > https://github.com/oblac/jodd/issues/329
> > > > https://github.com/oblac/jodd/pull/330
> > > > https://github.com/oblac/jodd/issues/331
> > > > https://github.com/oblac/jodd/pull/332
> > > >
> > > >
> > > >
> > > >> On my side I would like if possible to fix:
> > > >>> https://bz.apache.org/bugzilla/show_bug.cgi?id=60015
> > > >>>
> > > >> +1 to wait to the fix
> > > >>
> > > >> It may not be simple.
> > > >
> > > >
> > > >>
> > > >>> I have asked a question on dev mailing list.
> > > >>>
> > > >>> I have seen your mail but I don't see question
> > > >>
> > > >> I was waiting for remarks on analysis.
> > > > I may not have the whole picture.
> > > >
> > > >
> > > >> But if too complex we can wait for 3.2
> > > >>>
> > > >>> Regards
> > > >>>
> > > >>>
> > > >>>
> > > >>> On Tue, Sep 27, 2016 at 11:40 PM, Milamber <
> milam...@apache.org>
> > > >>>
> > > >> wrote:
> > > 
> > > > Hello,
> > > 
> > >  Ready? I can start the RC1 the 2nd October?
> > > 
> > >  Are you ok?
> > > 
> > >  Milamber
> > > 
> > > 
> > >  On 13/09/2016 15:20, Milamber wrote:
> > > 
> > >  Hello,
> > > >
> > > > Are you willing to start the next release process withing 1
> to
> > 2
> > > >
> > >  weeks?
> > > >>
> > > >>> I
> > > >>>
> > >  can act as RM.
> > > >
> > > > The next release will keep the Java 7 support (probably this
> > > >
> > >  release
> > > 
> > > > will
> > > >>>
> > > 

[GitHub] jmeter issue #231: WIP: timer that produces poisson arrivals with given cons...

[ra0077]

Github user ra0077 commented on the issue:

https://github.com/apache/jmeter/pull/231
  
Hi Vladimir,

No idea for the UI

Anybody have the answer?

To help me to understand how to use it, can you provide me some JMeter jmx 
file for each goal ("Specific number of iterations per hour", "Bursty 
load") with a short description (in comment)?

Thank
Antonio


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Report / Dashboard : New table Top 5 errors per sampler available on Dashboard

[Antonio Gomes Rodrigues]

Great

Antonio

2016-10-20 22:44 GMT+02:00 Philippe Mouawad :

> Hello,
> I have commited a new table which displays for each sampler in error the
> Top 5 errors:
>
>- https://bz.apache.org/bugzilla/show_bug.cgi?id=60287
>
> See screenshot here:
>
>- https://bz.apache.org/bugzilla/attachment.cgi?id=34393
>
>
> Feedback is welcome.
> Regards
> Philippe
>

[GitHub] jmeter issue #233: Bug 60274

[blindio]

Github user blindio commented on the issue:

https://github.com/apache/jmeter/pull/233
  
I look forward to your feedback


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---