[GitHub] jmeter issue #233: Bug 60274

Github user blindio commented on the issue: https://github.com/apache/jmeter/pull/233 The reason that I do not rely on the seed is because, as I understand it, you can count on seed to be consistent within am implementation of random, but not across implementations.

[GitHub] jmeter issue #233: Bug 60274

Github user blindio commented on the issue: https://github.com/apache/jmeter/pull/233 That is strange about the nesting not working, given that I manually tested nesting, and it is one of the unit tests as well. I will investigate. On Nov 13, 2016 12:08 AM, "Vladimir

Re: buildbot failure in on jmeter-trunk

Hi, Can we upgrade ant on build bot ? Do you plan the release today ? Thanks On Sunday, November 13, 2016, Milamber wrote: > > I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7) > > > > On 12/11/2016 20:41, Philippe Mouawad wrote: > >> Hello, >> I

[GitHub] jmeter issue #233: Bug 60274

Github user vlsi commented on the issue: https://github.com/apache/jmeter/pull/233 Just in case, C and C1 has the following groovy post-processor: `vars.put("x", String.valueOf(1+Integer.parseInt(vars.get("x"` --- If your project is set up for it, you can reply to this email and

Re: buildbot failure in on jmeter-trunk

I can reproduce this error with Ant 1.8.4. (works fine with Ant 1.9.7) On 12/11/2016 20:41, Philippe Mouawad wrote: Hello, I don't know how to fix this issue on buildbox. It's not happening on jenkins. Regards On Sat, Nov 12, 2016 at 4:23 PM, wrote: The Buildbot has

Re: buildbot failure in on jmeter-trunk

On 13/11/2016 10:04, Philippe Mouawad wrote: Hi, Can we upgrade ant on build bot ? I don't know. The error come because the call of org.apache.jorphan.test.AllTests in _test task don't have the jacocoagent property (with ant 1.8). Currently I try to find a bypass like the test.headless

[GitHub] jmeter issue #233: Bug 60274

Github user vlsi commented on the issue: https://github.com/apache/jmeter/pull/233 > I will test and consider a solution The question is if that is feasible at all to support run-time variable changes and keep the performance sane --- If your project is set up for it, you

[GitHub] jmeter issue #233: Bug 60274

Github user vlsi commented on the issue: https://github.com/apache/jmeter/pull/233 While being able to enable-disable and rename the children from WDC UI is nice, I wonder how many worms are hidden in that "keep WDC and children tree" consistent can. Nested "Weighted

[GitHub] jmeter issue #233: Bug 60274

Github user blindio commented on the issue: https://github.com/apache/jmeter/pull/233 Regarding the run time variable changes, that is a really good point. I will test and consider a solution. Thank you, Thorson On Nov 12, 2016 11:39 PM, "Vladimir

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

Am 13. November 2016 17:37:00 MEZ, schrieb Milamber : > > >On 13/11/2016 13:06, sebb wrote: >> On 13 November 2016 at 12:40, Felix Schumacher >> wrote: >>> Am 13.11.2016 13:34, schrieb Milamber: Hello, With commit 1769490, I

JMeter not mirrored to github since 6 days

Hi, I've created this ticket for that: https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-12906 Regards Philippe

BEFORE RELEASE CHECK : SVN Properties

Hello, Currently Readme.md has no svn properties. Shouldn't it have svn:eol : native ? Also I think README is referenced when building instead of README.md. Regards Philippe M

Re: BEFORE RELEASE CHECK : SVN Properties

On Sun, Nov 13, 2016 at 5:19 PM, Felix Schumacher < felix.schumac...@internetallee.de> wrote: > > > Am 13. November 2016 18:13:41 MEZ, schrieb Philippe Mouawad < > philippe.moua...@gmail.com>: > >Hello, > >Currently Readme.md has no svn properties. > >Shouldn't it have svn:eol : native ? > > Yes.

Re: BEFORE RELEASE CHECK : SVN Properties

Am 13. November 2016 18:13:41 MEZ, schrieb Philippe Mouawad : >Hello, >Currently Readme.md has no svn properties. >Shouldn't it have svn:eol : native ? Yes. Native seems to be right. > > >Also I think README is referenced when building instead of README.md. Don't

Re: BEFORE RELEASE CHECK : SVN Properties

Am 13. November 2016 18:20:52 MEZ, schrieb Philippe Mouawad : >On Sun, Nov 13, 2016 at 5:19 PM, Felix Schumacher < >felix.schumac...@internetallee.de> wrote: > >> >> >> Am 13. November 2016 18:13:41 MEZ, schrieb Philippe Mouawad < >> philippe.moua...@gmail.com>: >>

[GitHub] jmeter issue #233: Bug 60274

Github user blindio commented on the issue: https://github.com/apache/jmeter/pull/233 Agreed, I need to find some time to consider this issue. I may be that the variable resolution is not feasible without major changes. Again, thank you, Thorson On Nov

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

Hello, With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter. I've open a Infra ticket [1] to have a more recent version of Ant for the CI buildbot task. (currently I thinks it's Ant 1.8.2) Already says, this issue isn't a blocker for the 3.1 RC3. I will start the release process

Re: svn commit: r1769411 - /jmeter/trunk/src/components/org/apache/jmeter/visualizers/TableVisualizer.java

Hi, Yes sync on a new object is better. Note this wrong combination is present in code at many places. Regards On Sun, Nov 13, 2016 at 1:47 PM, sebb wrote: > Might be better to synch on a separate Object e.g.: > > private final Object LOCK = new Object(); > > On 13 November

Re: buildbot failure in on jmeter-trunk

Root cause : "The if/unless namespaces are only available since Ant 1.9.1." the if/unless namespaces was introduced with Bugzilla 60364 http://stackoverflow.com/questions/35393545/how-can-i-provide-a-conditional-jvmarg-for-the-ant-junit-command On 13/11/2016 10:23, Milamber wrote: On

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

Am 13.11.2016 13:34, schrieb Milamber: Hello, With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter. I've open a Infra ticket [1] to have a more recent version of Ant for the CI buildbot task. (currently I thinks it's Ant 1.8.2) Already says, this issue isn't a blocker for the 3.1

Re: buildbot failure in on jmeter-trunk [Tag: Ant, Buildbot]

On 13 November 2016 at 12:40, Felix Schumacher wrote: > Am 13.11.2016 13:34, schrieb Milamber: >> >> Hello, >> >> With commit 1769490, I force the usage of Ant > 1.9.1 for JMeter. >> >> I've open a Infra ticket [1] to have a more recent version of Ant for >> the

Re: svn commit: r1769411 - /jmeter/trunk/src/components/org/apache/jmeter/visualizers/TableVisualizer.java

Might be better to synch on a separate Object e.g.: private final Object LOCK = new Object(); On 13 November 2016 at 12:45, Felix Schumacher wrote: > Am 12.11.2016 21:29, schrieb pmoua...@apache.org: >> >> Author: pmouawad >> Date: Sat Nov 12 20:29:20 2016 >>

Re: svn commit: r1769411 - /jmeter/trunk/src/components/org/apache/jmeter/visualizers/TableVisualizer.java

Am 12.11.2016 21:29, schrieb pmoua...@apache.org: Author: pmouawad Date: Sat Nov 12 20:29:20 2016 New Revision: 1769411 URL: http://svn.apache.org/viewvc?rev=1769411=rev Log: Sync on final field Modified: jmeter/trunk/src/components/org/apache/jmeter/visualizers/TableVisualizer.java

Re: [VOTE] Release JMeter 3.1 RC3

+1 ! Andrey Pokhilko On 11/13/2016 11:34 AM, Milamber wrote: > Hello, > > The third release candidate for JMeter 3.1 (r1769531) 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

[VOTE] Release JMeter 3.1 RC3

Hello, The third release candidate for JMeter 3.1 (r1769531) 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 7/8 on Linux/Windows/Mac OS, especially on