You're right, that was the issue. Thanks for the tip! I'll remember not to download zips on Linux again. Although, I'd wish instead of remembering there was a mechanism in place that would make this unnecessary :) * there was a note on the download page and/or * Test that failed was smarter, for example diff that caused test to fail was ignoring line endings
Thanks! max On Thu, Feb 16, 2012 at 12:04 AM, Milamber <[email protected]> wrote: > > > Le 16/02/2012 07:34, max a ecrit : >> Hi, I just downloaded latest JMeter (2.6) on my Linux desktop and >> > > Have you downloaded the source file tgz ? or zip ? > tgz is the good archive to compile on Linux (works for me) > > Milamber > >> wanted to compile it from the source, however ran into what seems like >> a silly issue. >> >> 'ant test' failed with the following message: >> >> batch_scripts: >> >> batchtest: >> [echo] Starting HTMLParserTestFile_2 using -X >> [jmeter] Created the tree successfully using >> testfiles/HTMLParserTestFile_2.jmx >> [jmeter] Starting the test @ Wed Feb 15 22:38:01 PST 2012 (1329374281828) >> [jmeter] Waiting for possible shutdown message on port 4445 >> [jmeter] Tidying up ... @ Wed Feb 15 22:38:02 PST 2012 (1329374282977) >> [jmeter] ... end of run >> >> BUILD FAILED >> ./jmeter/build.xml:2163: The following error occurred while executing this >> line: >> ./jmeter/build.xml:2136: XML Files are not identical. >> ./jmeter/bin/testfiles/HTMLParserTestFile_2.xml >> ./jmeter/bin/HTMLParserTestFile_2.xml >> >> Total time: 2 minutes 24 seconds >> >> Upon closer inspection of these two XML files I found that they are >> different by 112 characters, i.e. exactly by the number of lines. >> Which implies that one file is using CR for newline (Linux style) and >> another (probably predefined) CRLF (Windows style). >> >> % wc ./bin/HTMLParserTestFile_2.xml ./bin/testfiles/HTMLParserTestFile_2.xml >> 112 355 7550 ./bin/HTMLParserTestFile_2.xml >> 112 355 7662 ./bin/testfiles/HTMLParserTestFile_2.xml >> >> Is this supposed to work on Linux / am I doing something wrong? Is >> there a property I can set to work around this? Is this a silly bug? >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Thanks, Maksym Kovalenko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
