Re: [I] Response data is included in XML reports even when the Save Response Data configuration option is de-selected [jmeter]

dbaer727 commented on issue #5980: URL: https://github.com/apache/jmeter/issues/5980#issuecomment-1861745682 I figured out what was causing this. The setting "Functional Test Mode" in the Test Plan and the "Save Response Data (XML)" in the Sample Result Save Configuration will both turn on

Re: [I] Issue with JDBC Connection Configuration in Jmeter 5.6.2 [jmeter]

vlsi commented on issue #6174: URL: https://github.com/apache/jmeter/issues/6174#issuecomment-1861148060 The root cause is `${__time(-MM-dd hh:mm:sss)}` You should have `ss` instead of `sss`. In any case, you'd better use query parameters rather than building the string with

Re: Release 5.6.3

Thanks to your work Still ok for me Le lun. 18 déc. 2023 à 16:19, Vladimir Sitnikov a écrit : > I've prepared the changelog for 5.6.3: > https://github.com/apache/jmeter/pull/6190 > > I suggest releasing 5.6.3 and moving to 6.0 development. > > Any thoughts? > > Vladimir >

Re: [I] Issue with JDBC Connection Configuration in Jmeter 5.6.2 [jmeter]

johnqa commented on issue #6174: URL: https://github.com/apache/jmeter/issues/6174#issuecomment-1860820518 Please find attached the problematic jmx. [MSSQL_BugTest.zip](https://github.com/apache/jmeter/files/13705546/MSSQL_BugTest.zip) -- This is an automated message from the

Build failed in Jenkins: JMeter » JMeter-trunk #740

See Changes: [Vladimir Sitnikov] fix: avoid NPE when ConstantTimer.delay accesses a variable -- [...truncated 113.91 KB...] > Task

Re: Release 5.6.3

I've prepared the changelog for 5.6.3: https://github.com/apache/jmeter/pull/6190 I suggest releasing 5.6.3 and moving to 6.0 development. Any thoughts? Vladimir

Re: [I] Constant Timer strange behavior when used with variables or functions [jmeter]

vlsi closed issue #6162: Constant Timer strange behavior when used with variables or functions URL: https://github.com/apache/jmeter/issues/6162 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Jenkins build is back to normal : JMeter » JMeter s390x #143

See

Re: [I] Constant Timer strange behavior when used with variables or functions [jmeter]

vlsi commented on issue #6162: URL: https://github.com/apache/jmeter/issues/6162#issuecomment-1860725495 The list of impacted classes is: `ConstantTimer` (and derived classes), `CompareAssertion`, `CSVDataSet`, `RandomVariableConfig` -- This is an automated message from the Apache Git

Re: [I] The Constant Throughput Timer is throwing a NullPointerException when using variables (vars.get) in "Target Throughput"-field [jmeter]

vlsi closed issue #6165: The Constant Throughput Timer is throwing a NullPointerException when using variables (vars.get) in "Target Throughput"-field URL: https://github.com/apache/jmeter/issues/6165 -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [PR] fix: allow usage of variables in ConstantThroughputTimer.throughput and PreciseThroughputTimer [jmeter]

vlsi merged PR #6192: URL: https://github.com/apache/jmeter/pull/6192 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org

[PR] fix: allow usage of variables in ConstantThroughputTimer.throughput and PreciseThroughputTimer [jmeter]

vlsi opened a new pull request, #6192: URL: https://github.com/apache/jmeter/pull/6192 Previously, the timers might fail initialization in case variable was not present when test started. The current workaround is to avoid implementing TestStateListener in the timers so JMeter does

Re: [I] The Constant Throughput Timer is throwing a NullPointerException when using variables (vars.get) in "Target Throughput"-field [jmeter]

vlsi commented on issue #6165: URL: https://github.com/apache/jmeter/issues/6165#issuecomment-1860158198 ## Root cause 1) `ConstantThroughputTimer` implements TestStateListener as it wants to reset state when the test begins 2) ConstantThroughputTimer is TestBean, so JMeter

Re: [I] Issue with JDBC Connection Configuration in Jmeter 5.6.2 [jmeter]

vlsi commented on issue #6174: URL: https://github.com/apache/jmeter/issues/6174#issuecomment-1860020320 Please attach the test plan that reproduces the issue -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[PR] docs: update changelog for 5.6.3 [jmeter]

vlsi opened a new pull request, #6190: URL: https://github.com/apache/jmeter/pull/6190 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: