Hi Graham, My answers below. On Fri, Jan 5, 2018 at 9:56 AM, Graham Russell <gra...@ham1.co.uk> wrote:
> I agree. > > The batch tests are so slow, partly because they run in sequence. It would > be good to make sure they are actually useful tests and add/remove as > necessary. > Yes they are: - They act as integration tests - They increase coverage of JUnit only tests by a high percentage > I was looking into running them in parallel, and found it easier with > gradle. Gradle can also import the existing ant script and seems to work, > at least for testing and building tasks. > > I will submit a PR if using gradle seems useful to slowly phase out ant? > We have the choice between Maven and Gradle. Emilian Bold proposed to move to Maven. I have more experience with it than gradle, I thought initially it would be hard with maven but it seems he thought differently. When I look at gradle a while ago, I felt documentation was not that wide. But if you are willing to do this move and document/help if we have questions in a reasonable timing (which is currently the case but might change in the future) I am ok for such PR. I'll be happy to increase my knowledge of Gradle. > I think it will make a few things easier and more standard/modern. > > I agree Or we can try to change the runner and then use the parallel ant task? > It a short term option . > > I don't have much time this month but should be able to help in February. > ok > > Graham > > > On Fri, 5 Jan 2018, 15:14 Philippe Mouawad, <philippe.moua...@gmail.com> > wrote: > > > Spock tests added. > > Maybe we’ll need to optimize build a bit as it takes now nearly half an > > hour to build > > > > On Friday, January 5, 2018, Philippe Mouawad <philippe.moua...@gmail.com > > > > wrote: > > > > > Hi, > > > See: > > > https://bz.apache.org/bugzilla/show_bug.cgi?id=61966 > > > > > > We need to add Spock tests > > > > > > Regards > > > > > > On Fri, Jan 5, 2018 at 12:33 AM, Philippe Mouawad < > > > philippe.moua...@gmail.com> wrote: > > > > > >> Hello, > > >> This is not currently configured on jenkins as a post-build task. > > >> > > >> As we run junit test using java task, the XML files required for the > > >> report are not generated. > > >> There is a task "complete-junit" that would generate results, but > > >> currently it runs tests without required configuration which leads to > > >> errors/ failures: > > >> > > >> - https://builds.apache.org/job/JMeter-trunk/6575/testReport/ > > >> - https://builds.apache.org/job/JMeter-trunk/test_results_ > analyzer/ > > >> > > >> If you'd like to contribute an enhancement to build, feel free to do > so. > > >> > > >> Regards > > >> > > >> On Wed, Jan 3, 2018 at 2:55 PM, jmeter tea <jmeter...@gmail.com> > wrote: > > >> > > >>> Hello, > > >>> > > >>> Test Results Analyzer in Jenkins isn't working for JMeter > > >>> https://builds.apache.org/job/JMeter-trunk/test_results_analyzer/ > > >>> > > >>> It's working in other other projects as: > > >>> https://builds.apache.org/job/HBase-Flaky-Tests/test_ > results_analyzer/ > > >>> > > >>> FYI > > >>> > > >> > > >> > > >> > > >> -- > > >> Cordialement. > > >> Philippe Mouawad. > > >> > > >> > > >> > > > > > > > > > -- > > > Cordialement. > > > Philippe Mouawad. > > > > > > > > > > > > > -- > > Cordialement. > > Philippe Mouawad. > > > -- Cordialement. Philippe Mouawad.
