Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Felix Schumacher
Am 1. Juli 2018 22:39:47 MESZ schrieb Igor Sasovets : >Here is console ouput. The snippet from your output below points at a problem in your gui setup. [java] There was 1 failure: [java] 1) errorDetected(org.apache.jmeter.testbeans.gui.PackageTest) [java] junit.framework.Assert

buildbot success in on jmeter-nightly

2018-07-01 Thread buildbot
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/1085 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: The Nightly scheduler

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Igor Sasovets
Here is console ouput. Best regards, Igor [java] java.rmi.server.hostname=null [java] Security framework of XStream not initialized, XStream is probably v ulnerable. [java] Security framework of XStream not initialized, XStream is probably v ulnerable. [java] Security framewor

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Felix Schumacher
Am 1. Juli 2018 21:03:15 MESZ schrieb Igor Sasovets : >I used ant test [-Djava.awt.headless=true] command What did the command produce? Hint there are no tests for the Mongo sampler, so it is unlikely, that any changes on that part should produce test errors. Regards, Felix > >Нд, 1 лип

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Igor Sasovets
I used ant test [-Djava.awt.headless=true] command Нд, 1 лип. 2018 21:38 користувач Felix Schumacher < felix.schumac...@internetallee.de> пише: > > > Am 01.07.2018 um 19:55 schrieb Igor Sasovets: > > Felix, I fixed problems with built. These issues appeared due to > deprecated > > methods in mong

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Felix Schumacher
Am 01.07.2018 um 19:55 schrieb Igor Sasovets: Felix, I fixed problems with built. These issues appeared due to deprecated methods in mongo-java-driver. But now I'm trying to find failed test. How I can exactly know which test failed because test name not displayed in console? Test failures s

[GitHub] jmeter issue #390: Update mongo-java-driver version

2018-07-01 Thread IgorSasovets
Github user IgorSasovets commented on the issue: https://github.com/apache/jmeter/pull/390 @FSchumacher , there were problems related to deprecated methods in mongo-java-driver, I fixed it. How I can get failed unit test name? ---

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Igor Sasovets
Felix, I fixed problems with built. These issues appeared due to deprecated methods in mongo-java-driver. But now I'm trying to find failed test. How I can exactly know which test failed because test name not displayed in console?

Build failed in Jenkins: JMeter Ubuntu #488

2018-07-01 Thread Apache Jenkins Server
See Changes: [fschumacher] Update to current jacoco version 0.8.1 -- [...truncated 172.52 KB...] [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on po

Re: PR390 - update mongo-java-driver version

2018-07-01 Thread Felix Schumacher
Am 01.07.2018 um 10:08 schrieb Igor Sasovets: Hi, Team! Recently I opened PR to apache/jmeter github repository: https://github.com/apache/jmeter/pull/390. Main aim of this PR is to allow users apply JMeter for projects which use MongoDB database. I wanted to test my application that uses Mon

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

2018-07-01 Thread Apache Jenkins Server
See

buildbot success in on jmeter-trunk

2018-07-01 Thread 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/3816 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler sc

[GitHub] jmeter issue #390: Update mongo-java-driver version

2018-07-01 Thread FSchumacher
Github user FSchumacher commented on the issue: https://github.com/apache/jmeter/pull/390 I always build with Oracle JDK 8 (u171 at the moment). ant version is 1.10.3. I suspect that you have an old mongo db jar lying around in your build path. ---

buildbot failure in on jmeter-trunk

2018-07-01 Thread 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/3815 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler sched

Build failed in Jenkins: JMeter-trunk #6820

2018-07-01 Thread Apache Jenkins Server
See Changes: [fschumacher] Try to get travis-ci back to green by adding oracle jdks for 10 and 11 -- [...truncated 194.67 KB...] [jmeter] ... end of run [echo] TEST_H

PR390 - update mongo-java-driver version

2018-07-01 Thread Igor Sasovets
Hi, Team! Recently I opened PR to apache/jmeter github repository: https://github.com/apache/jmeter/pull/390. Main aim of this PR is to allow users apply JMeter for projects which use MongoDB database. I wanted to test my application that uses MongoDB database using JMeter but faced with problems

buildbot success in on jmeter-trunk

2018-07-01 Thread 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/3811 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler sc

[GitHub] jmeter issue #390: Update mongo-java-driver version

2018-07-01 Thread IgorSasovets
Github user IgorSasovets commented on the issue: https://github.com/apache/jmeter/pull/390 @FSchumacher, I can try your updates and provide feedback. Also, please provide your Java and ant versions. Maybe this caused errors during build process. ---