I think I have found the Windows issue. Instead of failing, the test code logs a message if it cannot find the properties file:
2017-04-10 11:46:32,771 ERROR o.a.j.r.d.ApdexPerTransactionTest: Problem loading properties. java.io.FileNotFoundException: F:\jenkins\jenkins-slave\workspace\JMeter%20Windows\trunk\test\resources\org\apache\jmeter\report\dashboard\reportgenerator_test.properties (The system cannot find the path specified) I suspect this may be due to the space in the path name. @Milamber Perhaps you could try that locally? I know we recommend not to use spaces, but we should try and fix such issues when they become apparent. The test should fail if the file cannot be found. [I wonder how many other test cases use the same strategy.] On 10 April 2017 at 13:04, sebb <seb...@gmail.com> wrote: > There are also frequent failures with the Ubuntu builds in the test: > > TestSchedulerWithTimer > > This is possibly a timing issue, but again I don't think it's a good > idea to ignore such errors. > > I have added an extra test to try and debug the Windows failure - it > looks like the Props collection is empty. > > On 10 April 2017 at 11:14, sebb <seb...@gmail.com> wrote: >> On 10 April 2017 at 08:07, Milamber <milam...@apache.org> wrote: >>> >>> On my Windows 10 virtual machine, I built successfully JMeter from svn >>> trunk. I don't why we have this issue... The Jenkins machine is a Windows >>> 2012 R2, perhaps they have some differences with Windows 10 for this test? >> >> Possibly. >> But JMeter users may have the same problem, so the failure cannot just >> be ignored. >> >> We need to know what the cause is. >> It may perhaps be specific to the Jenkins build, but that seems unlikely. >> >>> >>> On 10/04/2017 01:58, sebb wrote: >>>> >>>> The last few Windows builds have failed with >>>> >>>> >>>> testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest) >>>> [java] java.lang.AssertionError: >>>> expected:<sample(\d+):1000|2000;samples12:3000|4000;scenar01-12:5000|6000> >>>> but was:<null> >>>> >>>> >>>> Has anyone investigated that? >>>> >>>> On 9 April 2017 at 17:31, Milamber <milam...@apache.org> wrote: >>>>> >>>>> Hello, >>>>> >>>>> The third release candidate for JMeter 3.2 (r1790748) has been prepared, >>>>> and >>>>> your votes are solicited. >>>>> >>>>> This release brings new features and fixes bugs. >>>>> >>>>> Please, test this release candidate (with load tests and/or functional >>>>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. >>>>> The >>>>> feedback are welcome. >>>>> >>>>> You can read the New and Noteworthy section with some screenshots to >>>>> illustrate improvements and full list of changes at: >>>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html >>>>> >>>>> JMeter is a Java desktop application designed to load test functional >>>>> behavior and measure performance. The current version is targeted at Java >>>>> 8+. >>>>> >>>>> Download - Archives/hashes/sigs: >>>>> >>>>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/ >>>>> (dist revision r19091) >>>>> >>>>> RAT report: >>>>> >>>>> >>>>> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt >>>>> >>>>> MD5 hashes of archives for this vote: >>>>> >>>>> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz >>>>> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip >>>>> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz >>>>> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip >>>>> >>>>> Site Docs are here: >>>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/ >>>>> >>>>> Maven staging repository is accessible here: >>>>> >>>>> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/ >>>>> >>>>> Tag: >>>>> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/ >>>>> >>>>> Keys are here: >>>>> https://www.apache.org/dist/jmeter/KEYS >>>>> >>>>> N.B. >>>>> To download the dependencies: "ant download_jars" >>>>> >>>>> To create the jars and test JMeter: "ant package test". >>>>> >>>>> JMeter 3.2 requires Java 8 or later to run. >>>>> >>>>> Some known issues and incompatible changes are listed on changes page. >>>>> >>>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds >>>>> >>>>> >>>>> All feedback and vote are welcome. >>>>> >>>>> [ ] +1 I support this release >>>>> [ ] +0 I am OK with this release >>>>> [ ] -0 OK, but.... >>>>> [ ] -1 I do not support this release (please indicate why) >>>>> >>>>> The vote will remain open for at least 72 hours. >>>>> >>>>> The PMC members please indicate the mention "(binding)" with your vote. >>>>> >>>>> >>>>> Note: If the vote passes, the intention is to release the archive files >>>>> and rename the RC tag as the release tag. >>>>> >>>>> Thanks in advance! >>>>> >>>>> Milamber >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>
