jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: buildbot failure in on jmeter-trunk
Date Sun, 09 Oct 2016 10:04:23 GMT
As has already been mentioned, the purpose of the test is to detect
accidental changes to the JMX format.

If the change is deliberate, then the test needs to be fixed.

However I think it should be fixed by deriving a new test from the old
one, and replacing that in the list of tests.
This is particularly true of the GenTest*.jmx files which were
auto-generated from the relevant versions.

The build file has a 'generator_jar' target:

ant generator_jar
Run JMeter Gui
Add a Thread Group
Add the Test Generator to the WorkBench
Run the Test Generator
Save the JMX



On 8 October 2016 at 12:34, Philippe Mouawad <philippe.mouawad@gmail.com> wrote:
> Thanks Felix.
> I am not sure either .
> I remember we need to create a special jmx file for every version (that
> changes save configuration ?).
>
> Sebb knows how to manage this I think.
> I think we need to document this somewhere .
>
> Regards
> Philippe
>
> On Sat, Oct 8, 2016 at 12:43 PM, Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Am Freitag, den 07.10.2016, 23:26 +0200 schrieb Philippe Mouawad:
>> > Hi,
>> > Anybody could guide me on how to fix the issue with:
>> >
>> >      [java] Loading file testfiles/GuiTest.jmx and saving it back
>> > changes its size from 44884 to 44879.
>> >      [java]
>> >      [java] Loading file testfiles/GuiTest231.jmx and saving it back
>> > changes its size from 65545 to 65524.
>> >      [java]
>> >      [java] Loading file testfiles/GenTest27.jmx and saving it back
>> > changes its size from 80101 to 80080.
>> >      [java]
>> >      [java] Loading file testfiles/GenTest210.jmx and saving it back
>> > changes its size from 86563 to 86542.
>> >      [java]
>> >      [java] Loading file testfiles/GenTest2_13.jmx and saving it back
>> > changes its size from 87218 to 87197.
>> >
>> > Any existing documentation on this ?
>>
>> I think these are used to test backwards compatibility of JMeter. Since
>> we broke it with this commit, they will have to be adapted (which I
>> already did).
>>
>> I don't know, if it is the right thing to do, either.
>>
>> Regards,
>>  Felix
>>
>> >
>> > Thanks
>> >
>> >
>> >
>> > On Fri, Oct 7, 2016 at 11:22 PM, <buildbot@apache.org> wrote:
>> >
>> > >
>> > > 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/1479
>> > >
>> > > Buildbot URL: https://ci.apache.org/
>> > >
>> > > Buildslave for this Build: hemera_ubuntu
>> > >
>> > > Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-
>> > > commit'
>> > > triggered this build
>> > > Build Source Stamp: [branch jmeter/trunk] 1763837
>> > > Blamelist: pmouawad
>> > >
>> > > BUILD FAILED: failed shell_3
>> > >
>> > > Sincerely,
>> > >  -The Buildbot
>> > >
>> > >
>> > >
>> > >
>> >
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Mime
View raw message