Build failed in Jenkins: JMeter-trunk #6676

See -- [...truncated 396.83 KB...] [echo] Checking xmlpull-1.1.3.1.jar [echo] Deleting xmlpull-* (excluding xmlpull-1.1.3.1.jar) setproxy: _get_jarfile: [echo] Fetching:

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

See

Build failed in Jenkins: JMeter Windows #1014

See Changes: [fschumacher] Don't start a new JVM for each junit test when using complete-junit This cuts down the time to complete the junit tests considerably. It takes less then two minutes on my machine.

[GitHub] jmeter pull request #376: Logging of JUnitSampler exceptions

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

Re: svn commit: r1824355 - in /jmeter/trunk: src/junit/org/apache/jmeter/protocol/java/sampler/JUnitSampler.java xdocs/changes.xml

Am 15.02.2018 um 21:35 schrieb Philippe Mouawad: On Thursday, February 15, 2018, Felix Schumacher < felix.schumac...@internetallee.de> wrote: Am Donnerstag, den 15.02.2018, 21:27 +0100 schrieb Philippe Mouawad: Hi Felix, Can’t this have an impact on performances leading to a lot of error

nightly builds (maven upload)

Hi all, the nightly builds have been moved to a new build node and the compilation and tests are working again (jay), but maven upload of the snapshot artefacts is failing: [java] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy-file (default-cli) on

Re: nightly builds (maven upload)

On 15 February 2018 at 20:53, Felix Schumacher wrote: > Hi all, > > the nightly builds have been moved to a new build node and the compilation > and tests are working again (jay), but maven upload of the snapshot > artefacts is failing: > > [java] [ERROR] Failed

Re: svn commit: r1824355 - in /jmeter/trunk: src/junit/org/apache/jmeter/protocol/java/sampler/JUnitSampler.java xdocs/changes.xml

Hi Felix, Can’t this have an impact on performances leading to a lot of error logging ? Regards On Thursday, February 15, 2018, wrote: > Author: fschumacher > Date: Thu Feb 15 20:09:16 2018 > New Revision: 1824355 > > URL: http://svn.apache.org/viewvc?rev=1824355=rev >

Re: svn commit: r1824355 - in /jmeter/trunk: src/junit/org/apache/jmeter/protocol/java/sampler/JUnitSampler.java xdocs/changes.xml

Am Donnerstag, den 15.02.2018, 21:27 +0100 schrieb Philippe Mouawad: > Hi Felix, > Can’t this have an impact on performances leading to a lot of error > logging > ? I don't think that the JUnitSampler is used for performance testing. If it is, I hope that the testers will be smart enough to

Re: svn commit: r1824355 - in /jmeter/trunk: src/junit/org/apache/jmeter/protocol/java/sampler/JUnitSampler.java xdocs/changes.xml

On Thursday, February 15, 2018, Felix Schumacher < felix.schumac...@internetallee.de> wrote: > Am 15.02.2018 um 21:35 schrieb Philippe Mouawad: > >> On Thursday, February 15, 2018, Felix Schumacher < >> felix.schumac...@internetallee.de> wrote: >> >> Am Donnerstag, den 15.02.2018, 21:27 +0100

[GitHub] jmeter issue #376: Logging of JUnitSampler exceptions

Github user FSchumacher commented on the issue: https://github.com/apache/jmeter/pull/376 Some discussion about the performance impact of the log messages has taken place on the dev mailing list. Would this patch be still useful for you, if we logged the messages at debug or

[GitHub] jmeter issue #376: Logging of JUnitSampler exceptions

Github user FSchumacher commented on the issue: https://github.com/apache/jmeter/pull/376 Thanks for your contribution. ---

Re: svn commit: r1824355 - in /jmeter/trunk: src/junit/org/apache/jmeter/protocol/java/sampler/JUnitSampler.java xdocs/changes.xml

On Thursday, February 15, 2018, Felix Schumacher < felix.schumac...@internetallee.de> wrote: > Am Donnerstag, den 15.02.2018, 21:27 +0100 schrieb Philippe Mouawad: > > Hi Felix, > > Can’t this have an impact on performances leading to a lot of error > > logging > > ? > > I don't think that the

Build failed in Jenkins: JMeter Windows #1015

See -- [...truncated 499.69 KB...] [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445 [jmeter] summary = 2 in 00:00:31 =0.1/s Avg: 15280

Build failed in Jenkins: JMeter-trunk #6678

See Changes: [fschumacher] Set eol-style to native -- [...truncated 188.83 KB...] [concat] 2018-02-15 19:03:28,181 WARN o.a.j.p.t.s.TCPSampler: Could not create socket

[GitHub] jmeter issue #376: Logging of JUnitSampler exceptions

Github user dfa1 commented on the issue: https://github.com/apache/jmeter/pull/376 Thanks to you for accepting this change. Naturally It would be still useful at info or debug level: the important point imho is to see the complete stacktrace when a test throws an exception.

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

See

Build failed in Jenkins: JMeter Windows #1016

See Changes: [fschumacher] We have three header divs (not four), so space them correctly [fschumacher] JUnitSampler logs exceptions except assertion-failures from test cases as warnings. Contributed by Davide