buildbot success in on jmeter-nightly

The Buildbot has detected a restored build on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/881 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_1604_test_ubuntu Build Reason: The Nightly

[GitHub] jmeter pull request #368: Csv sample reader fix

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/368 ---

[GitHub] jmeter issue #368: Csv sample reader fix

Github user codecov-io commented on the issue: https://github.com/apache/jmeter/pull/368 # [Codecov](https://codecov.io/gh/apache/jmeter/pull/368?src=pr=h1) Report > Merging [#368](https://codecov.io/gh/apache/jmeter/pull/368?src=pr=desc) into

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

Github user vlsi commented on the issue: https://github.com/apache/jmeter/pull/231 > Philippe: It is just that as per your confirmation, one of the aims of this new component was: > Vladimir: "The very basic requirement is to ensure you end up exactly 50 iterations **per hour**.

[GitHub] jmeter pull request #368: Csv sample reader fix

GitHub user ham1 opened a pull request: https://github.com/apache/jmeter/pull/368 Csv sample reader fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/ham1/jmeter CsvSampleReader_fix Alternatively you can review and apply

[GitHub] jmeter issue #365: Expanded Checkstyle to files in src and test; fixed newly...

Github user codecov-io commented on the issue: https://github.com/apache/jmeter/pull/365 # [Codecov](https://codecov.io/gh/apache/jmeter/pull/365?src=pr=h1) Report > Merging [#365](https://codecov.io/gh/apache/jmeter/pull/365?src=pr=desc) into

[GitHub] jmeter issue #366: Set max line length to 160 (eventual target 120).

Github user codecov-io commented on the issue: https://github.com/apache/jmeter/pull/366 # [Codecov](https://codecov.io/gh/apache/jmeter/pull/366?src=pr=h1) Report > Merging [#366](https://codecov.io/gh/apache/jmeter/pull/366?src=pr=desc) into

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

Github user pmouawad commented on the issue: https://github.com/apache/jmeter/pull/231 Hi @vlsi , Thanks for your clarifications. It is just that as per your confirmation, one of the aims of this new component was: **"The very basic requirement is to ensure you end up

[GitHub] jmeter pull request #367: Improved SampleMetadataParserSpec

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/367 ---

[GitHub] jmeter issue #367: Improved SampleMetadataParserSpec

Github user codecov-io commented on the issue: https://github.com/apache/jmeter/pull/367 # [Codecov](https://codecov.io/gh/apache/jmeter/pull/367?src=pr=h1) Report > Merging [#367](https://codecov.io/gh/apache/jmeter/pull/367?src=pr=desc) into

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

Github user vlsi commented on the issue: https://github.com/apache/jmeter/pull/231 >Is it really supposed to be exact ? Let me ask another question: "is thread scheduler=120sec supposed to make the test to last exactly 120 seconds"? Note: **timers do not limit the

Jenkins build is back to normal : JMeter Windows #951

See

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

Github user pmouawad commented on the issue: https://github.com/apache/jmeter/pull/231 Hi @vlsi , Thanks for your feedback. I tried many configurations including thread delay to 0, and I never really reach exact sampling on duration. Is it really supposed to be exact ?

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

See

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

Build failed in Jenkins: JMeter-trunk #6559

See Changes: [pmouawad] Bug 61900 - Report Generator : Report generation fails if separator is a regex reserved char like '|' Bugzilla Id: 61900 [pmouawad] Add files being compiled [pmouawad] Ignore failing test

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

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

Build failed in Jenkins: JMeter-trunk #6558

See Changes: [pmouawad] Bug 61759 - New __changeCase function Remove useless message labels as per orimarko patch Bugzilla Id: 61759 -- [...truncated 142.60 KB...]

[GitHub] jmeter pull request #366: Set max line length to 160 (eventual target 120).

GitHub user ham1 opened a pull request: https://github.com/apache/jmeter/pull/366 Set max line length to 160 (eventual target 120). ## Description Added new checkstyle rule for max line length of 160; with the view to, eventually, make it around 120. I will create another PR