[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-16 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322028#comment-322028 ] nkeywal commented on SUREFIRE-968: -- The single line one has the advantage of beeing easier to

[jira] (SUREFIRE-969) Log line on screen output

2013-03-09 Thread nkeywal (JIRA)
nkeywal created SUREFIRE-969: Summary: Log line on screen output Key: SUREFIRE-969 URL: https://jira.codehaus.org/browse/SUREFIRE-969 Project: Maven Surefire Issue Type: Bug

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-12-16 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315774#comment-315774 ] nkeywal commented on SUREFIRE-800: -- Would it be a solution to limit the usage of this

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-12-13 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315619#comment-315619 ] nkeywal commented on SUREFIRE-800: -- Thanks a lot for all this, Kristian.

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-12-12 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315526#comment-315526 ] nkeywal commented on SUREFIRE-800: -- Hi Kristian, Any news on this? Thanks!

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-11-12 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313393#comment-313393 ] nkeywal commented on SUREFIRE-800: -- Hi Kristian, Did you have some time to look at this jira?

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-09-19 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309041#comment-309041 ] nkeywal edited comment on SUREFIRE-800 at 9/19/12 8:05 AM: --- 2.12.3: cat

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-09-19 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309041#comment-309041 ] nkeywal commented on SUREFIRE-800: -- 2.12.3: cat

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-09-12 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308333#comment-308333 ] nkeywal commented on SUREFIRE-800: -- Hi Kristian, Any feedback on this patch? I think it fixes

[jira] (SUREFIRE-909) Wrong elapsed time calculation

2012-09-03 Thread nkeywal (JIRA)
nkeywal created SUREFIRE-909: Summary: Wrong elapsed time calculation Key: SUREFIRE-909 URL: https://jira.codehaus.org/browse/SUREFIRE-909 Project: Maven Surefire Issue Type: Bug

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-08-23 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-800: - Attachment: 800.v1.patch Hi Kristian, In 800.v1.patch, I tried the NonConcurrentReportManager approach, it

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-08-14 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306133#comment-306133 ] nkeywal commented on SUREFIRE-800: -- Thanks for the reply, it's a bad news for us... It seems

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-08-13 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306080#comment-306080 ] nkeywal commented on SUREFIRE-800: -- Hello Kristian, I had a look at the fix and its revert, I

[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always

2012-01-25 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289612#comment-289612 ] nkeywal commented on SUREFIRE-799: -- Yes, I confirm it will relaunch a new jvm for each test.

[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always

2012-01-24 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289548#comment-289548 ] nkeywal commented on SUREFIRE-799: -- Kristian renamed it to perthread in the trunk. It works well

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2012-01-08 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287749#comment-287749 ] nkeywal commented on SUREFIRE-800: -- This one is great! Thanks for all your help, Kristian.

[jira] (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

2012-01-01 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287216#comment-287216 ] nkeywal commented on SUREFIRE-798: -- As a side effect as well, note that when a forked process

[jira] (SUREFIRE-813) Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests.

2011-12-27 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286915#comment-286915 ] nkeywal commented on SUREFIRE-813: -- Yes, it's consistent:we have many lines (~100) logged during

[jira] (SUREFIRE-813) Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests.

2011-12-27 Thread nkeywal (JIRA)
nkeywal created SUREFIRE-813: Summary: Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests. Key: SUREFIRE-813 URL: https://jira.codehaus.org/browse/SUREFIRE-813

[jira] (SUREFIRE-813) Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests.

2011-12-27 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286925#comment-286925 ] nkeywal commented on SUREFIRE-813: -- What you mean for LogicalStream line 81 is that it's

[jira] (SUREFIRE-813) Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests.

2011-12-27 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286930#comment-286930 ] nkeywal commented on SUREFIRE-813: -- Yep, with the synchronized all the events are received by

[jira] (SUREFIRE-813) Randomly wrong tests count and empty summary files with JUnitProvider47 when forking the tests.

2011-12-27 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286939#comment-286939 ] nkeywal commented on SUREFIRE-813: -- After more tests, I confirm it works well with the

[jira] (SUREFIRE-773) surefire forked processes not always killed after timeout

2011-12-27 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286961#comment-286961 ] nkeywal commented on SUREFIRE-773: -- It's easy to reproduce with a sleep like this: {noformat}

[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always

2011-12-16 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-799: - Attachment: surefire_799.v2.patch Allow test parallelisation when forkMode=always

[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always

2011-12-16 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286121#comment-286121 ] nkeywal commented on SUREFIRE-799: -- v2 includes: - integration test with

[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider

2011-12-14 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285891#comment-285891 ] nkeywal commented on SUREFIRE-800: -- Note that with category implementation, we're now using

[jira] (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-12-14 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285895#comment-285895 ] nkeywal commented on SUREFIRE-793: -- I have a partial fix for it: with the fix, the time reported

[jira] (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-12-14 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285911#comment-285911 ] nkeywal commented on SUREFIRE-793: -- I checked, you're right, this works with forkMode=always

[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always

2011-12-12 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285597#comment-285597 ] nkeywal commented on SUREFIRE-799: -- Ok, will do. Do you have something in mind for 2.12 release

[jira] (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-12-12 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285600#comment-285600 ] nkeywal commented on SUREFIRE-793: -- Hi Kristian, You changed the priority to minor (which is

[jira] Updated: (SUREFIRE-799) Allow test parallelisation when forkMode=always

2011-12-08 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-799: - Attachment: surefire_799_212_trunk.patch Allow test parallelisation when forkMode=always

[jira] Commented: (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-12-05 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284967#comment-284967 ] nkeywal commented on SUREFIRE-793: -- The original issue is fixed, thank you! The difference

[jira] Created: (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

2011-11-26 Thread nkeywal (JIRA)
JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish. -- Key: SUREFIRE-798 URL:

[jira] Created: (SUREFIRE-799) Allow test parallelisation when forkMode=always

2011-11-26 Thread nkeywal (JIRA)
Allow test parallelisation when forkMode=always --- Key: SUREFIRE-799 URL: https://jira.codehaus.org/browse/SUREFIRE-799 Project: Maven Surefire Issue Type: Improvement Components: Junit

[jira] Created: (SUREFIRE-800) redirectTestOutputToFile is not taken into account with JUnit47 provider

2011-11-26 Thread nkeywal (JIRA)
redirectTestOutputToFile is not taken into account with JUnit47 provider Key: SUREFIRE-800 URL: https://jira.codehaus.org/browse/SUREFIRE-800 Project: Maven Surefire

[jira] Commented: (SUREFIRE-800) redirectTestOutputToFile is not taken into account with JUnit47 provider

2011-11-26 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284302#comment-284302 ] nkeywal commented on SUREFIRE-800: -- Seems that I can't edit the title. It should be: not taken

[jira] Commented: (SUREFIRE-760) mvn -Dtest=ClassName#methodName does not work with parallel tests

2011-11-26 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284303#comment-284303 ] nkeywal commented on SUREFIRE-760: -- Thanks a lot for the fix, Kristian! mvn

[jira] Commented: (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

2011-11-26 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284310#comment-284310 ] nkeywal commented on SUREFIRE-798: -- Yes, it's when running in serial. I understand that in

[jira] Created: (SUREFIRE-796) JUnit47 provider does not take into account the test method specified on the command line or the .pom

2011-11-25 Thread nkeywal (JIRA)
JUnit47 provider does not take into account the test method specified on the command line or the .pom - Key: SUREFIRE-796 URL:

[jira] Updated: (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-11-18 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-793: - Attachment: surefire_793_trunk.v3.patch I've managed to reduce the changes to something small. Imperfect

[jira] Created: (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report

2011-11-17 Thread nkeywal (JIRA)
JUnit47 provider reports incorrect time in the XML report - Key: SUREFIRE-793 URL: https://jira.codehaus.org/browse/SUREFIRE-793 Project: Maven Surefire Issue Type: Bug

[jira] Created: (SUREFIRE-791) JUnit47 provider reports incorrect elapsed time on test failure.

2011-11-16 Thread nkeywal (JIRA)
JUnit47 provider reports incorrect elapsed time on test failure. Key: SUREFIRE-791 URL: https://jira.codehaus.org/browse/SUREFIRE-791 Project: Maven Surefire Issue Type: Bug

[jira] Created: (SUREFIRE-789) Junit Category: Tests without category fail with the message initializationError(org.junit.runner.manipulation.Filter) when groups is set and forkMode=always

2011-11-12 Thread nkeywal (JIRA)
Junit Category: Tests without category fail with the message initializationError(org.junit.runner.manipulation.Filter) when groups is set and forkMode=always

[jira] Created: (SUREFIRE-786) JUnit @Category are not taken into account if forkMode=always

2011-11-10 Thread nkeywal (JIRA)
JUnit @Category are not taken into account if forkMode=always - Key: SUREFIRE-786 URL: https://jira.codehaus.org/browse/SUREFIRE-786 Project: Maven Surefire Issue Type: Bug

[jira] Updated: (SUREFIRE-786) JUnit @Category are not taken into account if forkMode=always

2011-11-10 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-786: - Attachment: surefire786_trunk.patch The patch fixes the issue for the classes. Only the needed class tests

[jira] Issue Comment Edited: (SUREFIRE-786) JUnit @Category are not taken into account if forkMode=always

2011-11-10 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283206#comment-283206 ] nkeywal edited comment on SUREFIRE-786 at 11/10/11 8:28 AM: The patch

[jira] Commented: (SUREFIRE-329) Support for JUNIT extensions

2011-11-09 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283160#comment-283160 ] nkeywal commented on SUREFIRE-329: -- Hi Kristian, thanks for having integrated the functionality.

[jira] Commented: (SUREFIRE-329) Support for JUNIT extensions

2011-11-08 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283030#comment-283030 ] nkeywal commented on SUREFIRE-329: -- I tested the branch SUREFIRE329 above on Apache HBase,

[jira] Updated: (SUREFIRE-329) Support for JUNIT extensions

2011-11-08 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated SUREFIRE-329: - Attachment: SUREFIRE329_branch329.patch patch on top of the branch 329. Support for JUNIT extensions

[jira] Commented: (SUREFIRE-329) Support for JUNIT extensions

2011-11-01 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282509#comment-282509 ] nkeywal commented on SUREFIRE-329: -- Kristian: Could you share the result of the tests you