Build failed in Jenkins: JMeter-trunk #5859

See Changes: [mchassagneux] Preserve encoding of test file -- [...truncated 1085 lines...] [javadoc] Loading source files for package org.apache.jmeter.testbeans... [javadoc] Loading source

[GitHub] jmeter issue #241: Support variable for all JMS messages (bytes, object, ......

Github user max3163 commented on the issue: https://github.com/apache/jmeter/pull/241 Closed with the 1783319 commit --- 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

Build failed in Jenkins: JMeter-trunk #5858

See Changes: [mchassagneux] Fix Checkstyle and Test failure for JMS -- [...truncated 1159 lines...] [javadoc] Loading source files for package org.apache.jmeter.examples.sampler.gui...

Re: svn commit: r1783297 - in /jmeter/trunk: src/core/org/apache/jmeter/ src/core/org/apache/jmeter/gui/action/ src/core/org/apache/jmeter/resources/ xdocs/

Hi Maxime, Can you run package-and-check ? This will tell you that there are tab characters that make test fail. Also can you close the related PR ? We usually add in commit comments this to automatically close PR: - This closes PR #ID_OF_PR Regards Philippe On Thu, Feb 16, 2017 at 10:23

Build failed in Jenkins: JMeter-trunk #5857

See Changes: [mchassagneux] Support variable for all JMS messages (bytes, object, ...) and sources (file, folder) -- [...truncated 999 lines...] [anakia] Output:

Build failed in Jenkins: JMeter-trunk #5855

See Changes: [pmouawad] Bug 60727 - Drop commons-httpclient-3.1 and related elements Fix test failure Bugzilla Id: 60727 -- [...truncated 2523 lines...] [sonar:sonar] JavaClasspath initialization

[GitHub] jmeter pull request #241: Support variable for all JMS messages (bytes, obje...

Github user max3163 closed the pull request at: https://github.com/apache/jmeter/pull/241 --- 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

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

See

Re: Proposition for contribution

Hi folks, Is there anyone working in unit tests for JDBC protocol? If not, I'd like to take a look into it next week. Cheers, Woonsan On Fri, Jan 6, 2017 at 2:35 PM, Philippe Mouawad wrote: > Hello, > Thanks for your proposal. > Yes it is still up to date. > > You

Build failed in Jenkins: JMeter-trunk #5850

See Changes: [pmouawad] Added some translations for polish locale Contributed by Bartosz Siewnak This closes #276 -- [...truncated 1168 lines...] [javadoc] Loading source files for package

Rotating JTL file writer

Hello, I want to write into JTL file a lot of data (about 50 megabytes per a second). This file takes a lot of space on hard drive and fails tests because of "Not enough space" errors. I wrote a feature, that allows writing sequence of files, limited by number of samples per file. This enables

Proposition for contribution

Great ! I think you can go ahead There was a discussion about a mocking framework to use. Graham started something around spock, Felix proposed jmockit, I don't know if he started something. And I mentioned mockito2 but without producing anything ;) But maybe your work does not need a mocking

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

Build failed in Jenkins: JMeter-trunk #5853

See Changes: [pmouawad] Bug 60727 - Drop commons-httpclient-3.1 and related elements Contributed by UbikLoadPack support Bugzilla Id: 60727 -- [...truncated 1073 lines...] docs-api: [echo]

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

See

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

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

Hello I still don't fully understand how to manage the particular test TestSaveService#testLoadAndSave. I thought we had to Save for example with current version the file to SaveGenTest210.jmx I did that but it looks pretty different from existing one. I tried saving with a 3.1 version and it is

Build failed in Jenkins: JMeter-trunk #5854

See Changes: [pmouawad] Ignore failing test to generate nightly, will be enabled again [mchassagneux] Checks for listener output file existence Bugzilla Id: 58164 [pmouawad] Add revision infos --

[GitHub] jmeter issue #241: Support variable for all JMS messages (bytes, object, ......

Github user pmouawad commented on the issue: https://github.com/apache/jmeter/pull/241 Hello, Would it be possible to bench this with more threads than 2 ? 50 for example ? Would it be possible to wait for 3.2 release before merging this one ? Thanks --- If your

[GitHub] jmeter issue #247: Checks for listener output file existence

Github user pmouawad commented on the issue: https://github.com/apache/jmeter/pull/247 Merged with commit: http://svn.apache.org/viewvc?rev=1783297=rev This PR can be closed. Thanks --- If your project is set up for it, you can reply to this email and have your reply

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