Hello,
>From a twitter poll, it appears 13% of voters still need it.
@Users, if you're concerned, it would be nice to give some use cases for
your current usage.
Thanks
On Tuesday, January 31, 2017, Philippe Mouawad
wrote:
> Hello Users,
>
> We would like to
GitHub user woonsan opened a pull request:
https://github.com/apache/jmeter/pull/266
Migrating to SLF4J - components/visualizers package
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/woonsan/jmeter feature/bz60564-5
Github user squarebracket commented on the issue:
https://github.com/apache/jmeter/pull/261
I've added a test. I verified that it failed without the fix, passes with
it.
I also had to change around the test
GitHub user woonsan opened a pull request:
https://github.com/apache/jmeter/pull/265
Feature/bz60564 4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/woonsan/jmeter feature/bz60564-4
Alternatively you can review and apply
Github user woonsan commented on the issue:
https://github.com/apache/jmeter/pull/264
@pmouawad Thanks for the review! I totally overlooked the file being
recreated. Cheers!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user woonsan commented on the issue:
https://github.com/apache/jmeter/pull/263
@pmouawad I guess I didn't include the condition in case I thought the
method call was trivial, but you're totally right. Method call shouldn't be
avoided at any case in debug logging. Thank you
Github user asfgit closed the pull request at:
https://github.com/apache/jmeter/pull/264
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Philippe>But is comparison fair in this case ?
Well, of course it is.
It could make sense to integrate "UI freeze profiling" right into JMeter
code so we could identify those freezes and tame them.
For instance: take an automatic thread dump in case UI thread spends more
than 500ms when
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/263
Hi Woonsan,
Thanks for the PR.
I just modified few lines, I think I did right, but confirmation is better.
I added log.isDebugEnabled() when parameters of log message called some
GitHub user woonsan opened a pull request:
https://github.com/apache/jmeter/pull/264
Bug 60564 - Migrating to SLF4J logger - components/config,control,extractor
packages.
You can merge this pull request into a Git repository by running:
$ git pull
Github user squarebracket commented on the issue:
https://github.com/apache/jmeter/pull/261
That's a very good idea. I don't have very much experience with testing in
Java, but I'll see what I can manage. Is the Travis job the right command to
run for testing? (`ant
GitHub user woonsan opened a pull request:
https://github.com/apache/jmeter/pull/263
Bug 60564 - Migrating LogKit logger to SLF4J logger - only for
components/assertions package.
You can merge this pull request into a Git repository by running:
$ git pull
The Buildbot has detected a restored build on builder jmeter-trunk while
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/2137
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: bb_slave1_ubuntu
Build Reason: The AnyBranchScheduler
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/2135
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: bb_slave1_ubuntu
Build Reason: The AnyBranchScheduler
14 matches
Mail list logo