Re: buildbot failure in on jmeter-nightly

Am 14.02.2017 um 03:37 schrieb build...@apache.org: The Buildbot has detected a new failure on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/585 Buildbot URL: https://ci.apache.org/ Buildslave for this Build:

buildbot failure in on jmeter-nightly

The Buildbot has detected a new failure on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/585 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The Nightly scheduler

User defined variables at ThreadGroup scope

I am converting some code from the eggPlant test tool we've been using, which effectively supports properties or variables (essentially everything is a variable in its context) at the thread group (TG) level. It's a pretty useful feature, as typically I set up default props/vars for a test,

Re: Code Style Guidelines

Jeremiah>The project was internal and I cannot show it publicly. Can you clarify which kind of changes did take place? Was there a code movement (e.g. methods, variables, fields rearranged)? Class refactoring (e.g. method moved to another class)? There's no magic. git-blame can ignore

RE: Code Style Guidelines

> -Original Message- > From: Vladimir Sitnikov [mailto:sitnikov.vladi...@gmail.com] > Sent: Monday, February 13, 2017 10:20 AM > To: dev@jmeter.apache.org > Subject: Re: Code Style Guidelines > >> It kind of ruins git-blame output and tends to make understanding the >> scope of work in

RE: Code Style Guidelines

> From: Vladimir Sitnikov [mailto:sitnikov.vladi...@gmail.com] > Sent: Monday, February 13, 2017 4:00 AM > To: dev@jmeter.apache.org > Subject: Re: Code Style Guidelines > >> My experience is that code reformatting makes history browsing very much >> harder. > > Could you give any example here?

Re: Code Style Guidelines

On 13 February 2017 at 12:45, Vladimir Sitnikov wrote: > sebb>Attachments not present; they are dropped by most Apache mailing lists. > > Here's the same mail in Google docs with screenshots: >

Re: Code Style Guidelines

sebb>Attachments not present; they are dropped by most Apache mailing lists. Here's the same mail in Google docs with screenshots: https://docs.google.com/document/d/1-Yr_PEOhkLXS8ArKxRVVl-9b8l8Gj-5x0gdgmW5MyJ8/edit?usp=sharing sebb>AFAIK, that does not work in Eclipse Well, I might check how

buildbot success in on jmeter-nightly

The Buildbot has detected a restored build on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/584 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The Nightly scheduler

Re: Code Style Guidelines

On 13 February 2017 at 08:59, Vladimir Sitnikov wrote: > sebb>My experience is that code reformatting makes history browsing very > much harder. > > Could you give any example here? What particular use case breaks with > single-commit reformatting? > > Just to be

Re: Code Style Guidelines

sebb>My experience is that code reformatting makes history browsing very much harder. Could you give any example here? What particular use case breaks with single-commit reformatting? Just to be clear: I don't suggest to reformat the code to some completely alien format. I suggest to pick a

Re: AuthManager behaviour

For record, fixed in upcoming 3.2: https://bz.apache.org/bugzilla/show_bug.cgi?id=57242 Regards On Tue, Jul 30, 2013 at 9:28 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > Any answer on this ? > > Thanks > Regards > Philippe > > > On Sat, Jul 27, 2013 at 11:08 PM, Philippe