Re: Bug 58679 : blocker for next release

Hello, I created a test case not related to JMeter and submitted: - https://github.com/x-stream/xstream/issues/51 Jörg from XStream already answered: https://github.com/x-stream/xstream/issues/51#issuecomment-210155359

Jenkins build is back to normal : JMeter-trunk #5184

See

[GitHub] jmeter pull request: Bug59329_CSVDataSetTrimFilenamev2

GitHub user ra0077 opened a pull request: https://github.com/apache/jmeter/pull/196 Bug59329_CSVDataSetTrimFilenamev2 Hi, Like I have proposed in "Bug 56877 - CSVDataSet does not trim spaces in .csv", I split this issue into different PR/Issues to merge fix step by

[GitHub] jmeter pull request: Bug59328_BetterLabelAndToolTipInCSVDataSetVar...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/195 --- 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

[GitHub] jmeter pull request: Bug59305DefaultReportHTMLStatisticsColumnSort

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/193 --- 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

[GitHub] jmeter pull request: Bug59328_BetterLabelAndToolTipInCSVDataSetVar...

GitHub user ra0077 opened a pull request: https://github.com/apache/jmeter/pull/195 Bug59328_BetterLabelAndToolTipInCSVDataSetVariableNames Hi, in CSVDataSet if the variable name field is empty, then the first line of the file is read and interpreted as the list of

buildbot success in on jmeter-trunk

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/993 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The AnyBranchScheduler

[GitHub] jmeter pull request: Bug59304_Hamonize2labelsinHTMLReport

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/192 --- 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

Build failed in Jenkins: JMeter-trunk #5183

See Changes: [pmouawad] Bug 59293 - Better Axis to Latencies over Time graph in report Patch contributed by Antonio Gomes Rodrigues #resolve #185 Bugzilla Id: 59293 [pmouawad] Bug 59292 - Better Axis to Response time over Time graph in

[GitHub] jmeter pull request: Bug59293_AddAvgInAxisToLatenciesOverTimeRepor...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/185 --- 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

[GitHub] jmeter pull request: Bug59292_AddAvgInAxisToResponseTimeOverTimeRe...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/184 --- 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

[GitHub] jmeter pull request: Bug59298_BetterReportgenerator_summary_statis...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/190 --- 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

[GitHub] jmeter pull request: Bug 59281 testTimeDurationGUI

Github user pmouawad commented on the pull request: https://github.com/apache/jmeter/pull/182#issuecomment-210117693 Hi Antonio, I would be very interested by a UX Expert proposal on all JMeter GUI :-), not just this part. This would really help us, provided the advice is not

buildbot failure in on jmeter-trunk

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/989 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The AnyBranchScheduler

[GitHub] jmeter pull request: Bug59320 generic gui tooltipsv2

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/194 --- 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

[GitHub] jmeter pull request: Bug59305DefaultReportHTMLStatisticsColumnSort

Github user ra0077 commented on the pull request: https://github.com/apache/jmeter/pull/193#issuecomment-210115536 Hi, My opinion is "I want to see all my results in Statistics table sorted by transaction. And after that I want to sort it in response time and/or error%"

[GitHub] jmeter pull request: Bug 59281 testTimeDurationGUI

Github user ra0077 commented on the pull request: https://github.com/apache/jmeter/pull/182#issuecomment-210112763 Hi, My opinion is that it's not well integrated with the JMeter GUI. I prefer before (like I have made it with my PR) And because we don't must run laod

Re: Bug 58679 : blocker for next release

HI Milamber, How was this plan created ? For me it's not a blocker as the XML is wrong. But if we end up thinking it is a blocker, then let's revert the code and wait for 3.1 to "fix" this although I don't see how it can be. Regards On Thu, Apr 14, 2016 at 9:10 PM, Milamber

Bug 58679 : blocker for next release

Hello, Please see the Bug 58679, I've found a regression with the changes from xstream/xpp librairies. Error : missing class com.thoughtworks.xstream.converters.ConversionException: : ParseError at [row,col]: etc. If I revert the associated commits, my simple script works. Milamber

[GitHub] jmeter pull request: Bug 59281 testTimeDurationGUI

Github user pmouawad commented on the pull request: https://github.com/apache/jmeter/pull/182#issuecomment-210055924 I voluntarily made it like this because I found it more visible :-) So I don't know what to do with this PR. --- If your project is set up for it, you can reply to

[GitHub] jmeter pull request: Bug59303_NewDefaultResponseTimeDistributionGr...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/191 --- 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

[GitHub] jmeter pull request: Bug59305DefaultReportHTMLStatisticsColumnSort

Github user pmouawad commented on the pull request: https://github.com/apache/jmeter/pull/193#issuecomment-210050073 Hi, The choice was made to highlight transactions with upper error. So the sorting based on Error% looks ok for me. Clicking on the column to sort against

[GitHub] jmeter pull request: Bug59320 generic gui tooltipsv2

GitHub user ra0077 opened a pull request: https://github.com/apache/jmeter/pull/194 Bug59320 generic gui tooltipsv2 Hi, When you use GenericTestBeanCustomizer to create your GUI, the tooltip in French and Enflish have not the same form (in english we have a line

Re: Listing directory content with the FTPSampler

On Thursday, April 14, 2016, Pierre Roudier wrote: > Hi > > The current version is already backward compatible; it's quite easy to > implement. I'll make sure the new one remains compatible. Also ensure that: When you open a 2.13 plan in 3.1 and then close it, it does

Re: When can we start the release of 3.0 ?

Hi, Thanks to Felix and Milamber to have merged some of my PR. If you have time to merge the other, it's will be great too Antonio Garanti sans virus. www.avast.com

Re: Listing directory content with the FTPSampler

Hi The current version is already backward compatible; it's quite easy to implement. I'll make sure the new one remains compatible. Before I start the dev, what are the guidelines regarding JMeter UI? I'd like to know what screen size is targeted. The only doc fairly related I found is