Re: failing timeshift test

Am 08.03.20 um 13:56 schrieb Felix Schumacher: > Am 08.03.20 um 13:53 schrieb Vladimir Sitnikov: >>> interpretation of LocalTime addition operations and parsing >> Well, the function itself does a lot of time parsing, so I am nowhere sure >> if it contains bug or not. >> Did you mean the test

Build failed in Jenkins: JMeter Ubuntu #982

See Changes: [felix.schumacher] Apply autostyle to make spotbugs happy [sitnikov.vladimir] Bump vlsi-release-plugins: 1.61 -> 1.65 [sitnikov.vladimir] Add ExecutionMode.SAME_THREAD to JMeterSerialTest to ensure

Re: Darklaf - A themeable swing Look and Feel based on Darcula-Laf

On Thu, 5 Mar 2020 at 17:28, Vladimir Sitnikov wrote: > > >Properties, XML, etc are not executed by the JVM; they are effectively > >just data. > > BeanShell, JavaScript, and Groovy are not "just data", but it is code which > is a part of JMeter. > > So far I see no technical justification for

Jenkins build is back to normal : JMeter Windows #1634

See

Re: failing timeshift test

Am 08.03.20 um 13:53 schrieb Vladimir Sitnikov: >> interpretation of LocalTime addition operations and parsing > Well, the function itself does a lot of time parsing, so I am nowhere sure > if it contains bug or not. > Did you mean the test fails at the specific date only? Yes, my thinking was

Re: failing timeshift test

>interpretation of LocalTime addition operations and parsing Well, the function itself does a lot of time parsing, so I am nowhere sure if it contains bug or not. Did you mean the test fails at the specific date only? However, the concurrent execution of tests that alter timezone is not

Re: [jmeter] branch master updated: Apply autostyle to make spotbugs happy

Am 08.03.20 um 12:59 schrieb Vladimir Sitnikov: > Felix> new 1673248 Apply autostyle to make spotbugs happy > > 1) Technically speaking, this has nothing to do with spotbugs. You are probably right, but somehow I read spotbugs failing and the nice suggestion to use autostyleApply, so I

Re: failing timeshift test

Am 08.03.20 um 12:55 schrieb Vladimir Sitnikov: > I guess the issue there is the test relies on TimeZone.getDefault(), > however, > there's > org.apache.jmeter.functions.TestDateTimeConvertFunction#testDateTimeConvertEpochTime > which alters the default time zone. > > Let's see if something

Re: [jmeter] branch master updated: Apply autostyle to make spotbugs happy

Felix> new 1673248 Apply autostyle to make spotbugs happy 1) Technically speaking, this has nothing to do with spotbugs. 2) If you install editorconfig plugin, it would likely insert the final newline automatically (see insert_final_newline in .editorconfig) Vladimir

Re: failing timeshift test

I guess the issue there is the test relies on TimeZone.getDefault(), however, there's org.apache.jmeter.functions.TestDateTimeConvertFunction#testDateTimeConvertEpochTime which alters the default time zone. Let's see if something like https://github.com/apache/jmeter/pull/560 can workaround

Build failed in Jenkins: JMeter Windows #1633

See Changes: [felix.schumacher] Allow spaces in ${...} expressions around function calls. [felix.schumacher] Markup changes and a few minor typos [felix.schumacher] Apply autostyle to make spotbugs happy

Re: failing timeshift test

Am 07.03.20 um 14:56 schrieb Felix Schumacher: > Hi all, > > the test TestTimeShiftFunction#testNowWithComplexPeriod is failing > probably due to a transition period shortly before day light saving time > switch. Seems the test failed on travis and for jdk 13, only

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

See