Build failed in Jenkins: JMeter Windows #1495

See Changes: [sitnikov.vladimir] Fix ParallelResourcesAndIpSource for Windows -- [...truncated 143.29 KB...] Thread[/127.0.0.1:60313 to /127.0.0.1:60312 workers

Build failed in Jenkins: JMeter-trunk #7404

See Changes: [sitnikov.vladimir] Close StringFromFile after testing so Windows could remove temporary [sitnikov.vladimir] Fix ParallelResourcesAndIpSource for Windows --

Build failed in Jenkins: JMeter Windows #1494

See Changes: [sitnikov.vladimir] Close StringFromFile after testing so Windows could remove temporary -- [...truncated 153.58 KB...] > Task :src:core:check > Task

Build failed in Jenkins: JMeter-trunk #7403

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H29 (ubuntu xenial) in workspace /home/jenkins/jenkins-slave/workspace/JMeter-trunk No

Build failed in Jenkins: JMeter Windows #1493

See -- [...truncated 142.50 KB...] > Task :src:components:compileTestGroovy > Task :src:components:testClasses > Task :src:components:checkstyleTest > Task :src:components:spotbugsMain

Build failed in Jenkins: JMeter-trunk #7402

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H29 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7401

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H29 (ubuntu xenial) in workspace No

Re: Eclipse and hamcrest

I am not really looking at replacing hamcrest with something different (at the moment). Felix Am 28.09.19 um 20:56 schrieb Graham Russell: > If we were looking at replacements I like Google Truth, it's like AssertJ > but often with better error messages and with both the code reads more >

Re: Eclipse and hamcrest

If we were looking at replacements I like Google Truth, it's like AssertJ but often with better error messages and with both the code reads more naturally than Hamcrest imo e.g. assertThat(result).isEmpty(); Almost as good as Spock ;) result.isEmpty() On Sat, 28 Sep 2019, 17:30 Felix

Re: Build failed in Jenkins: JMeter Windows #1477

Felix>And now it is spotless against windows line endings. I wonder how will win :) The files were checked out with LF (I've downloaded CompareAssertionSpec.groovy) for some reason, and it caused the issue. For now, I cleaned the workspace and it should work OK. Vladimir

Build failed in Jenkins: JMeter Windows #1480

See -- [...truncated 36.23 KB...] > Task :src:examples:processResources > Task :src:examples:processTestResources NO-SOURCE > Task :src:examples:spotlessJava > Task

Build failed in Jenkins: JMeter Windows #1479

See -- [...truncated 38.65 KB...] - *\n - * Unless required by applicable law or agreed to in writing, software\n - * distributed under the License is

Re: Build failed in Jenkins: JMeter Windows #1477

And now it is spotless against windows line endings. I wonder how will win :) Felix Am 28. September 2019 19:30:25 MESZ schrieb Apache Jenkins Server : >See > > >Changes: > >[pmouawad] Suite > >[pmouawad]

Build failed in Jenkins: JMeter Windows #1478

See -- [...truncated 2.81 KB...] > Task :buildSrc:compileGroovy NO-SOURCE > Task :buildSrc:pluginDescriptors UP-TO-DATE > Task :buildSrc:processResources NO-SOURCE > Task

Re: build failures on jenkins

Ok, The key offender there was new SecureRandom().generateSeed(128) The test launches JMeter multiple times, and it caused lots of "generateSeed(128)" calls. I've removed excessive generateSeed(128), and I've made the initialization lazy. The stacktrace in question was is "main" #1 prio=5

Build failed in Jenkins: JMeter Windows #1477

See Changes: [pmouawad] Suite [pmouawad] Correct cleanup [pmouawad] JOrphanUtils: add random alphanumeric password generator [pmouawad] Bug 63355 - View Results Tree: Browser view option is not Available

Re: Jenkins build is back to normal : JMeter-trunk #7398

Hooray Felix Am 28. September 2019 19:20:20 MESZ schrieb Apache Jenkins Server : >See >

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

See

Re: Eclipse and hamcrest

Mark>From previous experience I would suggest switching to assertj I had something like that in my mind, however, it seemed too much to switch to another library for one or two use cases only. I think behind the lines of enabling Kotlin-based tests, however, that is a bit different story.

Re: Eclipse and hamcrest

>duplicate classpath entries (https://github.com/gradle/gradle/issues/10393 ). Is it fixed in Gradle 5.6.2? Should we update then? Vladimir

Re: Eclipse and hamcrest

Am 28.09.19 um 14:41 schrieb Vladimir Sitnikov: > I was a bit puzzled with java-hamcrest as well. > > It looks like we should exclude it: (see > https://github.com/hamcrest/JavaHamcrest/issues/183#issuecomment-441154016 > and >

Build failed in Jenkins: JMeter-trunk #7393

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7392

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7391

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7390

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7389

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7388

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7387

See -- Started by user vladimirsitnikov [EnvInject] - Loading node environment variables. Building remotely on H35 (ubuntu xenial) in workspace

Build failed in Jenkins: JMeter-trunk #7386

See -- [...truncated 604.23 KB...] Starting process 'command '/usr/local/asfpackages/java/jdk1.8.0_191/bin/java''. Working directory:

Build failed in Jenkins: JMeter-trunk #7384

See -- [...truncated 423.82 KB...] Thread[/0:0:0:0:0:0:0:1:57068 to /0:0:0:0:0:0:0:1:43874 workers Thread 2,5,main], stackTrace:sun.misc.Unsafe#park

Re: Eclipse and hamcrest

From previous experience I would suggest switching to assertj. It’s not pulled in by as many things so you are less likely to get wierd dependency conflicts and it provides useful output when things don’t match. Also it’s a fluent api so easy to discover the various matcher methods. Really

Re: Eclipse and hamcrest

I was a bit puzzled with java-hamcrest as well. It looks like we should exclude it: (see https://github.com/hamcrest/JavaHamcrest/issues/183#issuecomment-441154016 and http://hamcrest.org/JavaHamcrest/distributables#upgrading-from-hamcrest-1x ) Felix, would you please check if adding

Eclipse and hamcrest

Hi all, when I currently try to run the test TestJSONPostProcessor in eclipse as a junit test, it complaints about a missing method org.hamcrest.CoreMatchers.anyOf(...) I suspect that this is a result of too many hamcrest implementations/the wrong order of those implementations. Felix

Re: [jmeter] 02/03: Revert to correct logic for detecting lists

Am 28.09.19 um 13:12 schrieb Philippe Mouawad: > On Saturday, September 28, 2019, wrote: > >> This is an automated email from the ASF dual-hosted git repository. >> >> fschumacher pushed a commit to branch master >> in repository https://gitbox.apache.org/repos/asf/jmeter.git >> >> commit

Re: build failures on jenkins

On Sat, 28 Sep 2019 at 10:34, Felix Schumacher wrote: > > Hi all, > > it seems that the builds on jenkins are failing since the last good one > seven days ago > (https://builds.apache.org/blue/organizations/jenkins/JMeter-trunk/activity). > The jobs seem to be getting killed after 30 minutes. The