Re: Test Results Analyzer isn't working

[Philippe Mouawad]

Spock tests added.
Maybe we’ll need to optimize build a bit as it takes now nearly half an
hour to build

On Friday, January 5, 2018, Philippe Mouawad 
wrote:

> Hi,
> See:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=61966
>
> We need to add Spock tests
>
> Regards
>
> On Fri, Jan 5, 2018 at 12:33 AM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Hello,
>> This is not currently configured on jenkins as a post-build task.
>>
>> As we run junit test using java task, the XML files required for the
>> report are not generated.
>> There is a task "complete-junit" that would generate results, but
>> currently it runs tests without required configuration which leads to
>> errors/ failures:
>>
>>- https://builds.apache.org/job/JMeter-trunk/6575/testReport/
>>- https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/
>>
>> If you'd like to contribute an enhancement to build, feel free to do so.
>>
>> Regards
>>
>> On Wed, Jan 3, 2018 at 2:55 PM, jmeter tea  wrote:
>>
>>> Hello,
>>>
>>> Test Results Analyzer in Jenkins isn't working for JMeter
>>> https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/
>>>
>>> It's working in other other projects as:
>>> https://builds.apache.org/job/HBase-Flaky-Tests/test_results_analyzer/
>>>
>>> FYI
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: Test Results Analyzer isn't working

[Philippe Mouawad]

Hi,
See:
https://bz.apache.org/bugzilla/show_bug.cgi?id=61966

We need to add Spock tests

Regards

On Fri, Jan 5, 2018 at 12:33 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Hello,
> This is not currently configured on jenkins as a post-build task.
>
> As we run junit test using java task, the XML files required for the
> report are not generated.
> There is a task "complete-junit" that would generate results, but
> currently it runs tests without required configuration which leads to
> errors/ failures:
>
>- https://builds.apache.org/job/JMeter-trunk/6575/testReport/
>- https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/
>
> If you'd like to contribute an enhancement to build, feel free to do so.
>
> Regards
>
> On Wed, Jan 3, 2018 at 2:55 PM, jmeter tea  wrote:
>
>> Hello,
>>
>> Test Results Analyzer in Jenkins isn't working for JMeter
>> https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/
>>
>> It's working in other other projects as:
>> https://builds.apache.org/job/HBase-Flaky-Tests/test_results_analyzer/
>>
>> FYI
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Jenkins build is back to stable : JMeter-trunk #6576

[Apache Jenkins Server]

See 

Re: Test Results Analyzer isn't working

[Philippe Mouawad]

Hello,
This is not currently configured on jenkins as a post-build task.

As we run junit test using java task, the XML files required for the report
are not generated.
There is a task "complete-junit" that would generate results, but currently
it runs tests without required configuration which leads to errors/
failures:

   - https://builds.apache.org/job/JMeter-trunk/6575/testReport/
   - https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/

If you'd like to contribute an enhancement to build, feel free to do so.

Regards

On Wed, Jan 3, 2018 at 2:55 PM, jmeter tea  wrote:

> Hello,
>
> Test Results Analyzer in Jenkins isn't working for JMeter
> https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/
>
> It's working in other other projects as:
> https://builds.apache.org/job/HBase-Flaky-Tests/test_results_analyzer/
>
> FYI
>



-- 
Cordialement.
Philippe Mouawad.

buildbot success in on jmeter-trunk

[buildbot]

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

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

Build succeeded!

Sincerely,
 -The Buildbot

Jenkins build is unstable: JMeter-trunk #6575

[Apache Jenkins Server]

See 

Build failed in Jenkins: JMeter-trunk #6574

[Apache Jenkins Server]

See 


Changes:

[pmouawad] Add junit results (first test)

--
[...truncated 339.94 KB...]
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.166 sec
[junit] Running org.apache.jmeter.functions.TestRegexFunction
[junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.292 sec
[junit] Running org.apache.jmeter.functions.TestSamplerNameFunction
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.216 sec
[junit] Running org.apache.jmeter.functions.TestSetProperty
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.346 sec
[junit] Running org.apache.jmeter.functions.TestSimpleFunctions
[junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.072 sec
[junit] Running org.apache.jmeter.functions.TestTimeFunction
[junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.166 sec
[junit] Running org.apache.jmeter.functions.TestTimeRandomDateFunction
[junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.839 sec
[junit] Running org.apache.jmeter.functions.TestTimeShiftFunction
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.698 sec
[junit] Running org.apache.jmeter.functions.TestUrlEncodeDecode
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.183 sec
[junit] Running org.apache.jmeter.functions.VariableTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.286 sec
[junit] Running org.apache.jmeter.gui.action.TestLoad
[junit] Tests run: 80, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.934 sec
[junit] Running org.apache.jmeter.gui.action.TestSave
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.604 sec
[junit] Running org.apache.jmeter.gui.logging.TestGuiLogEventAppender
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.652 sec
[junit] Running org.apache.jmeter.gui.util.JSyntaxTextAreaTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.657 sec
[junit] Running org.apache.jmeter.junit.JMeterTest
[junit] Tests run: 708, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.374 sec
[junit] Running org.apache.jmeter.listeners.TestResultAction
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.072 sec
[junit] Running 
org.apache.jmeter.protocol.http.config.MultipartUrlConfigTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.991 sec
[junit] Running org.apache.jmeter.protocol.http.config.UrlConfigTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.133 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthManager
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.151 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthorization
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.213 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestCacheManagerHC4
[junit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
12.834 sec
[junit] Running 
org.apache.jmeter.protocol.http.control.TestCacheManagerUrlConnection
[junit] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
12.77 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestDNSCacheManager
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.428 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHC4CookieManager
[junit] Tests run: 33, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.448 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHTTPMirrorThread
[junit] Tests run: 9, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: 
0.862 sec
[junit] Test org.apache.jmeter.protocol.http.control.TestHTTPMirrorThread 
FAILED
[junit] Running 
org.apache.jmeter.protocol.http.control.gui.TestHttpTestSampleGui
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.571 sec
[junit] Running org.apache.jmeter.protocol.http.modifier.TestAnchorModifier
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.17 sec
[junit] Running 
org.apache.jmeter.protocol.http.modifier.TestURLRewritingModifier
[junit] Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.26 sec
[junit] Running org.apache.jmeter.protocol.http.parser.TestBaseParser
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.03 sec
[junit] Running 
org.apache.jmeter.protocol.http.parser.TestBug60842HtmlParser
[junit] Tests run: 42, Failures: 0, Errors: 

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

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

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot

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

[Apache Jenkins Server]

See 

Re: Controversial topic: Remove internationalization

[Antonio Gomes Rodrigues]

+1 to avoid mix of different languages (Having english forced in setup
instead of relying on default locale)

No opinion to remove translation

Antonio

2018-01-04 22:39 GMT+01:00 Andrey Pokhilko :

> Hi,
>
> +1 to become English-only. I agree to all of the reasoning by Philippe.
>
> Andrey Pokhilko
>
> 04.01.2018 19:31, Philippe Mouawad пишет:
> > Hello,
> >
> > Currently we provide ability to translate JMeter GUI in many languages.
> > In our tests we only ensure French translations are available because we
> > have french team members.
> >
> > For other languages, we are in best effort and most probably the UI looks
> > non professional for many users as there will be a mix of english and non
> > english labels.
> >
> > I am aware that it's a controversial topic and many people probably rely
> on
> > translated GUI BUT:
> >
> >- I dislike the fact that GUI looks non professional
> >- Why don't we have more translation contributions if they are used ?
> >- It's a certain piece of work to maintain and create those
> translations
> >
> > So unless there is a magical way to fully translate all labels and
> maintain
> > them efficiently, I am  in favor of:
> >
> >- Having english forced in setup instead of relying on default locale.
> >It seems this happened accidentally in 3.3 and nobody complained
> about it.
> >- In a second step, and unless there is a big move to help on
> >translation, I propose to drop all languages, even french one as it's
> an
> >additional work and we have other and a lot of things to do
> >
> >
> > Thoughts :-) ?
>
>

Re: Controversial topic: Remove internationalization

[Andrey Pokhilko]

Hi,

+1 to become English-only. I agree to all of the reasoning by Philippe.

Andrey Pokhilko

04.01.2018 19:31, Philippe Mouawad пишет:
> Hello,
>
> Currently we provide ability to translate JMeter GUI in many languages.
> In our tests we only ensure French translations are available because we
> have french team members.
>
> For other languages, we are in best effort and most probably the UI looks
> non professional for many users as there will be a mix of english and non
> english labels.
>
> I am aware that it's a controversial topic and many people probably rely on
> translated GUI BUT:
>
>- I dislike the fact that GUI looks non professional
>- Why don't we have more translation contributions if they are used ?
>- It's a certain piece of work to maintain and create those translations
>
> So unless there is a magical way to fully translate all labels and maintain
> them efficiently, I am  in favor of:
>
>- Having english forced in setup instead of relying on default locale.
>It seems this happened accidentally in 3.3 and nobody complained about it.
>- In a second step, and unless there is a big move to help on
>translation, I propose to drop all languages, even french one as it's an
>additional work and we have other and a lot of things to do
>
>
> Thoughts :-) ?

buildbot success in on jmeter-trunk

[buildbot]

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

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

Build succeeded!

Sincerely,
 -The Buildbot

Build failed in Jenkins: JMeter-trunk #6572

[Apache Jenkins Server]

See 


Changes:

[pmouawad] Bug 61899 - Report Generation : When 
"jmeter.save.saveservice.print_field_names" is false and sample_variables are 
set report generation fails
Contributed by UbikLoadPack
Bugzilla Id: 61899

--
[...truncated 453.10 KB...]
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.sampler.render...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.mongo...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.sampler...
  [javadoc] Constructing Javadoc information...
  [javadoc] Standard Doclet version 1.8.0_152
  [javadoc] Building tree for all the packages and classes...
  [javadoc] 
:44:
 error: reference not found
  [javadoc]  * See {@link AssertionGui} for GUI.
  [javadoc]   ^
  [javadoc] 
:981:
 warning: no description for @param
  [javadoc]  * @param listener
  [javadoc]^
  [javadoc] 
:989:
 warning: no description for @param
  [javadoc]  * @param listener
  [javadoc]^
  [javadoc] 
:203:
 warning: no @return
  [javadoc] public Sample readSample() {
  [javadoc]   ^
  [javadoc] 
:212:
 warning: no @return
  [javadoc] public Sample peek() {
  [javadoc]   ^
  [javadoc] 
:219:
 warning: no @return
  [javadoc] public boolean hasNext() {
  [javadoc]^
  [javadoc] 
:150:
 warning: no @param for threadNum
  [javadoc] public void setThreadNum(int threadNum) {
  [javadoc] ^
  [javadoc] 
:161:
 warning: no @param for thread
  [javadoc] public void setThread(JMeterThread thread) {
  [javadoc] ^
  [javadoc] 
:172:
 warning: no @param for threadgrp
  [javadoc] public void setThreadGroup(AbstractThreadGroup threadgrp) {
  [javadoc] ^
  [javadoc] 
:183:
 warning: no @param for engine
  [javadoc] public void setEngine(StandardJMeterEngine engine) {
  [javadoc] ^
  [javadoc] 
:194:
 warning: no @param for b
  [javadoc] public void setSamplingStarted(boolean b) {
  [javadoc] ^
  [javadoc] 
:201:
 warning: no @param for restartNextLoop
  [javadoc] public void setStartNextThreadLoop(boolean restartNextLoop) {
  [javadoc] ^
  [javadoc] 
:209:
 warning: no @return
  [javadoc] public boolean isStartNextThreadLoop() {
  [javadoc]^
  [javadoc] 
:220:
 warning: no @param for restartNextLoop
  [javadoc] public void setRestartNextLoop(boolean restartNextLoop) {
  [javadoc] ^
  [javadoc] 
:228:
 warning: no @return
  [javadoc] public boolean isRestartNextLoop() {
  [javadoc]^
  [javadoc] 
:254:
 

Re: Controversial topic: Remove internationalization

[Graham Russell]

I don't think translations should be removed. I think they add value to
those who do not have a good understanding of English. We don't have any
usage metrics so it's hard to tell how much they are used.

Regarding it being unprofessional, I agree, but I do not think it is an
issue, especially if English is now the default.

I guess that we don't have more contributions because of a lack of
awareness and perhaps a lack of desire from people who have the ability to
translate, because they can use the English.

We could try to make the community more aware that we need more
translations? Perhaps via Twitter or the users list etc. and see if this
helps. However we first need to make sure the translation guidance is
really simple and easy for people to follow.

Graham

On Fri, 5 Jan 2018 at 00:31 Philippe Mouawad 
wrote:

> Hello,
>
> Currently we provide ability to translate JMeter GUI in many languages.
> In our tests we only ensure French translations are available because we
> have french team members.
>
> For other languages, we are in best effort and most probably the UI looks
> non professional for many users as there will be a mix of english and non
> english labels.
>
> I am aware that it's a controversial topic and many people probably rely on
> translated GUI BUT:
>
>- I dislike the fact that GUI looks non professional
>- Why don't we have more translation contributions if they are used ?
>- It's a certain piece of work to maintain and create those translations
>
> So unless there is a magical way to fully translate all labels and maintain
> them efficiently, I am  in favor of:
>
>- Having english forced in setup instead of relying on default locale.
>It seems this happened accidentally in 3.3 and nobody complained about
> it.
>- In a second step, and unless there is a big move to help on
>translation, I propose to drop all languages, even french one as it's an
>additional work and we have other and a lot of things to do
>
>
> Thoughts :-) ?
> --
> Cordialement.
> Philippe Mouawad.
>

Build failed in Jenkins: JMeter-trunk #6571

[Apache Jenkins Server]

See 


Changes:

[rjung] Happy New Year 2018

[pmouawad] Bug 61931 - Precise Throughput Timer : timer that produces poisson 
arrivals with given constant throughput
Translate in french UI

Bugzilla Id: 61931

[pmouawad] Bug 61931 - Precise Throughput Timer : timer that produces poisson 
arrivals with given constant throughput
Forgot one file
Bugzilla Id: 61931

[pmouawad] Format for better readability

[pmouawad] Bug 61931 - Precise Throughput Timer : timer that produces poisson 
arrivals with given constant throughput
Contributed by Vladimir Sitnikov
This closes #369
Bugzilla Id: 61931

[pmouawad] Bug 61956 - Report Generation : -f of -forceDeleteResultFile option 
does not work
Bugzilla Id: 61956

--
[...truncated 453.10 KB...]
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.control.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.sampler...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.jms.sampler.render...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.system.gui...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.config...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.mongo...
  [javadoc] Loading source files for package 
org.apache.jmeter.protocol.mongodb.sampler...
  [javadoc] Constructing Javadoc information...
  [javadoc] Standard Doclet version 1.8.0_152
  [javadoc] Building tree for all the packages and classes...
  [javadoc] 
:44:
 error: reference not found
  [javadoc]  * See {@link AssertionGui} for GUI.
  [javadoc]   ^
  [javadoc] 
:981:
 warning: no description for @param
  [javadoc]  * @param listener
  [javadoc]^
  [javadoc] 
:989:
 warning: no description for @param
  [javadoc]  * @param listener
  [javadoc]^
  [javadoc] 
:181:
 warning: no @return
  [javadoc] public Sample readSample() {
  [javadoc]   ^
  [javadoc] 
:190:
 warning: no @return
  [javadoc] public Sample peek() {
  [javadoc]   ^
  [javadoc] 
:197:
 warning: no @return
  [javadoc] public boolean hasNext() {
  [javadoc]^
  [javadoc] 
:150:
 warning: no @param for threadNum
  [javadoc] public void setThreadNum(int threadNum) {
  [javadoc] ^
  [javadoc] 
:161:
 warning: no @param for thread
  [javadoc] public void setThread(JMeterThread thread) {
  [javadoc] ^
  [javadoc] 
:172:
 warning: no @param for threadgrp
  [javadoc] public void setThreadGroup(AbstractThreadGroup threadgrp) {
  [javadoc] ^
  [javadoc] 
:183:
 warning: no @param for engine
  [javadoc] public void setEngine(StandardJMeterEngine engine) {
  [javadoc] ^
  [javadoc] 
:194:
 warning: no @param for b
  [javadoc] public void setSamplingStarted(boolean b) {
  [javadoc] ^
  [javadoc] 
:201:
 warning: no @param for restartNextLoop
  [javadoc] public void setStartNextThreadLoop(boolean restartNextLoop) {
  [javadoc] ^
  [javadoc] 
:209:
 warning: no @return
  [javadoc] public boolean isStartNextThreadLoop() {
  [javadoc]^
  [javadoc] 
:220:
 warning: no @param 

Controversial topic: Remove internationalization

[Philippe Mouawad]

Hello,

Currently we provide ability to translate JMeter GUI in many languages.
In our tests we only ensure French translations are available because we
have french team members.

For other languages, we are in best effort and most probably the UI looks
non professional for many users as there will be a mix of english and non
english labels.

I am aware that it's a controversial topic and many people probably rely on
translated GUI BUT:

   - I dislike the fact that GUI looks non professional
   - Why don't we have more translation contributions if they are used ?
   - It's a certain piece of work to maintain and create those translations

So unless there is a magical way to fully translate all labels and maintain
them efficiently, I am  in favor of:

   - Having english forced in setup instead of relying on default locale.
   It seems this happened accidentally in 3.3 and nobody complained about it.
   - In a second step, and unless there is a big move to help on
   translation, I propose to drop all languages, even french one as it's an
   additional work and we have other and a lot of things to do


Thoughts :-) ?
-- 
Cordialement.
Philippe Mouawad.

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

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

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot

[GitHub] jmeter issue #369: docs: document Precise Throughput Timer

[pmouawad]

Github user pmouawad commented on the issue:

https://github.com/apache/jmeter/pull/369
  
Большое спасибо!!


---

[GitHub] jmeter pull request #369: docs: document Precise Throughput Timer

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/369


---

[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
  
@pmouawad , please review https://github.com/apache/jmeter/pull/369


---