[GitHub] jmeter pull request #428: Change Test Action (old name) to "Flow Control Act...

2018-11-06 Thread jmetertea 
GitHub user jmetertea opened a pull request:

https://github.com/apache/jmeter/pull/428

Change Test Action (old name) to "Flow Control Action" in Component 
Reference

Change Test Action (old name) to "Flow Control Action" in document

## Description
Change Test Action (old name) to "Flow Control Action" in document

## Motivation and Context
Document still uses old name "Test Action"

## How Has This Been Tested?
NA


## Types of changes
- Bug fix (non-breaking change which fixes an issue)

## Checklist:
- [X ] My code follows the [code style][style-guide] of this project.
- [X ] I have updated the documentation accordingly.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jmetertea/jmeter patch-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/428.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #428


commit 552ce4fb079be0f86b434f7dd7f5cf587e9d0742
Author: jmetertea <33323555+jmetertea@...>
Date:   2018-11-06T09:53:02Z

Update component_reference.xml

Change Test Action (old name) to "Flow Control Action" in document




---

[GitHub] jmeter issue #428: Change Test Action (old name) to "Flow Control Action" in...

2018-11-06 Thread codecov-io 
Github user codecov-io commented on the issue:

https://github.com/apache/jmeter/pull/428
  
# [Codecov](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=h1) 
Report
> Merging 
[#428](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=desc) into 
[trunk](https://codecov.io/gh/apache/jmeter/commit/1f32ed961d5e800b0228524d81a9a918d8b52ece?src=pr&el=desc)
 will **not change** coverage.
> The diff coverage is `n/a`.

[![Impacted file tree 
graph](https://codecov.io/gh/apache/jmeter/pull/428/graphs/tree.svg?width=650&token=6Q7CI1wFSh&height=150&src=pr)](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=tree)

```diff
@@Coverage Diff@@
##  trunk #428   +/-   ##
=
  Coverage 58.59%   58.59%   
  Complexity1063210632   
=
  Files  1196 1196   
  Lines 7604476044   
  Branches   7356 7356   
=
  Hits  4455944559   
  Misses2897928979   
  Partials   2506 2506
```



--

[Continue to review full report at 
Codecov](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=continue).
> **Legend** - [Click here to learn 
more](https://docs.codecov.io/docs/codecov-delta)
> `Δ = absolute  (impact)`, `ø = not affected`, `? = missing 
data`
> Powered by 
[Codecov](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=footer). Last 
update 
[1f32ed9...552ce4f](https://codecov.io/gh/apache/jmeter/pull/428?src=pr&el=lastupdated).
 Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments).



---

Build failed in Jenkins: JMeter-trunk #6959

2018-11-06 Thread Apache Jenkins Server 
See 


Changes:

[pmouawad] Bug 62806 ModuleController cloning by Run behaves differently wether 
in GUI or Non GUI mode.
Reinstate old method signature to avoid NoSuchMethodError in calling plugins 
and deprecate it
Bugzilla Id: 62806

--
[...truncated 608.75 KB...]
[junit] Running org.apache.jmeter.functions.TestMachineIPName
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.183 sec
[junit] Running org.apache.jmeter.functions.TestRandomFromMultipleVars
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.263 sec
[junit] Running org.apache.jmeter.functions.TestRegexFunction
[junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.219 sec
[junit] Running org.apache.jmeter.functions.TestSamplerNameFunction
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.129 sec
[junit] Running org.apache.jmeter.functions.TestSetProperty
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.165 sec
[junit] Running org.apache.jmeter.functions.TestSimpleFunctions
[junit] Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.315 sec
[junit] Running org.apache.jmeter.functions.TestTimeFunction
[junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.73 sec
[junit] Running org.apache.jmeter.functions.TestTimeRandomDateFunction
[junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.894 sec
[junit] Running org.apache.jmeter.functions.TestTimeShiftFunction
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.696 sec
[junit] Running org.apache.jmeter.functions.TestUrlEncodeDecode
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.153 sec
[junit] Running org.apache.jmeter.functions.VariableTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.06 sec
[junit] Running org.apache.jmeter.gui.action.TestLoad
[junit] Tests run: 85, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
6.936 sec
[junit] Running org.apache.jmeter.gui.action.TestSave
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.076 sec
[junit] Running org.apache.jmeter.gui.logging.TestGuiLogEventAppender
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.045 sec
[junit] Running org.apache.jmeter.gui.util.JSyntaxTextAreaTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.23 sec
[junit] Running org.apache.jmeter.junit.JMeterTest
[junit] Tests run: 715, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
44.565 sec
[junit] Running org.apache.jmeter.listeners.TestResultAction
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.247 sec
[junit] Running 
org.apache.jmeter.protocol.http.config.MultipartUrlConfigTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.112 sec
[junit] Running org.apache.jmeter.protocol.http.config.UrlConfigTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.089 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthManager
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.262 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthorization
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.01 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestCacheManagerHC4
[junit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.597 sec
[junit] Running 
org.apache.jmeter.protocol.http.control.TestCacheManagerUrlConnection
[junit] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.547 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestDNSCacheManager
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.709 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHC4CookieManager
[junit] Tests run: 33, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.957 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHTTPMirrorThread
[junit] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.098 sec
[junit] Running 
org.apache.jmeter.protocol.http.control.gui.TestHttpTestSampleGui
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.056 sec
[junit] Running org.apache.jmeter.protocol.http.modifier.TestAnchorModifier
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.967 sec
[junit] Running 
org.apache.jmeter.protocol.http.modifier.TestURLRewritingModifier
[junit] Tests run: 17, Failures: 0, Errors: 0, Skipped:

FAQ #18: I want to use “Monitor Results” of JMeter

2018-11-06 Thread Kashiwabara, Merrill 
Hello,

FAQ #18: I want to use “Monitor Results” of JMeter

The answer apparently predates the deprecation and removal of the "Monitor
Results" component and related documentation: it refers to the "Monitor
Results" component and the "Use as Monitor" flag on samplers.

The removal of this functionality poses a problem for those of use who
wrote tests which depended upon it.  The old components allowed reports to
include and correlate load with a variety of server metrics in a consistent
and reusable manner.  While there is a page on the wiki called Monitoring
Servers , it only
contains a three item list and only for Tomcat monitoring.
Going forward, what is the supported/expected method for monitoring server
resource consumption and server health during a load test?  Will there be
any enhancements to the current reporting to include server metrics with
the data collected by JMeter ?

-- 

*Merrill Kashiwabara*
Product Sr Software Quality Engineer II
ERT | 500 Rutherford Avenue | Boston, MA 02129 | USA
ert.com

[GitHub] jmeter issue #397: fix double requests when configure proxy with authenticat...

2018-11-06 Thread pmouawad 
Github user pmouawad commented on the issue:

https://github.com/apache/jmeter/pull/397
  
Hi Team,
Anybody had a chance to test this behind a proxy and under regular 
conditions ?

Thanks


---

[GitHub] jmeter pull request #411: SHA1 is alias for SHA-1, but SHA-1 would work in m...

2018-11-06 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/411


---

[GitHub] jmeter pull request #428: Change Test Action (old name) to "Flow Control Act...

2018-11-06 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/428


---

Build failed in Jenkins: JMeter-trunk #6960

2018-11-06 Thread Apache Jenkins Server 
See 


Changes:

[pmouawad] Change Test Action (old name) to "Flow Control Action" in Component 
Reference

Contributed by Ori Marko
This closes #428

[pmouawad] SHA1 is alias for SHA-1, but SHA-1 would work in most scenario

Contributed by pacoxu
This closes #411

[pmouawad] Try to improve javadoc

[pmouawad] Cleanup some SONAR warnings
Remove old TODO

--
[...truncated 554.58 KB...]
[junit] Running org.apache.jmeter.functions.TestMachineIPName
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.005 sec
[junit] Running org.apache.jmeter.functions.TestRandomFromMultipleVars
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.004 sec
[junit] Running org.apache.jmeter.functions.TestRegexFunction
[junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.014 sec
[junit] Running org.apache.jmeter.functions.TestSamplerNameFunction
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.003 sec
[junit] Running org.apache.jmeter.functions.TestSetProperty
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.003 sec
[junit] Running org.apache.jmeter.functions.TestSimpleFunctions
[junit] Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.028 sec
[junit] Running org.apache.jmeter.functions.TestTimeFunction
[junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.007 sec
[junit] Running org.apache.jmeter.functions.TestTimeRandomDateFunction
[junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.05 sec
[junit] Running org.apache.jmeter.functions.TestTimeShiftFunction
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.05 sec
[junit] Running org.apache.jmeter.functions.TestUrlEncodeDecode
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.004 sec
[junit] Running org.apache.jmeter.functions.VariableTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[junit] Running org.apache.jmeter.gui.action.TestLoad
[junit] Tests run: 85, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.086 sec
[junit] Running org.apache.jmeter.gui.action.TestSave
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.01 sec
[junit] Running org.apache.jmeter.gui.logging.TestGuiLogEventAppender
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.036 sec
[junit] Running org.apache.jmeter.gui.util.JSyntaxTextAreaTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.008 sec
[junit] Running org.apache.jmeter.junit.JMeterTest
[junit] Tests run: 715, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.72 sec
[junit] Running org.apache.jmeter.listeners.TestResultAction
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.004 sec
[junit] Running 
org.apache.jmeter.protocol.http.config.MultipartUrlConfigTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.005 sec
[junit] Running org.apache.jmeter.protocol.http.config.UrlConfigTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.003 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthManager
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.006 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestAuthorization
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.003 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestCacheManagerHC4
[junit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
12.802 sec
[junit] Running 
org.apache.jmeter.protocol.http.control.TestCacheManagerUrlConnection
[junit] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
12.664 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestDNSCacheManager
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.294 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHC4CookieManager
[junit] Tests run: 33, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.092 sec
[junit] Running org.apache.jmeter.protocol.http.control.TestHTTPMirrorThread
[junit] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.963 sec
[junit] Running 
org.apache.jmeter.protocol.http.control.gui.TestHttpTestSampleGui
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.029 sec
[junit] Running org.apache.jmeter.protocol.http.modifier.TestAnchorModifier
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.127 sec
[junit] Running 
org.apa

buildbot failure in on jmeter-nightly

2018-11-06 Thread buildbot 
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/1209

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave7_ubuntu

Build Reason: The Nightly scheduler named 'jmeterNightly' triggered this build
Build Source Stamp: [branch jmeter/trunk] HEAD
Blamelist: 

BUILD FAILED: failed shell_5

Sincerely,
 -The Buildbot