You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2010/07/16 02:09:51 UTC
[jira] Created: (AMQNET-263) Upgrade to NUnit 2.5.5
Upgrade to NUnit 2.5.5
----------------------
Key: AMQNET-263
URL: https://issues.apache.org/activemq/browse/AMQNET-263
Project: ActiveMQ .Net
Issue Type: Test
Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
Affects Versions: 1.4.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.4.0
Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60762#action_60762 ]
Jim Gomes edited comment on AMQNET-263 at 7/19/10 1:27 PM:
-----------------------------------------------------------
I think you must be. I just successfully ran all of the unit tests on Mono 2.6.4 on Windows 7. It seems like there was the normal number of pass/fail results, but I would have to double check to be sure. However, the tests all did run. My final result numbers were: "Passed: 416, Failed: 26, Errors: 3, Time: 568.95"
I do notice that there are some visual drawing anomolies of the NUnit interface when running under Mono, and if I click on the Text Output tab, an error dialog pops up.
How are you running the tests, and what version of Mono are you using? I am also running the .NET 3.5 build of the tests.
Update: I ran the tests again on .NET CLR, and the results are slightly different: "Passed: 418, Failed: 24, Errors: 3" There are two tests that fail on Mono, but pass on .NET. I'm not sure which they are or if that might be expected or not.
was (Author: semog):
I think you must be. I just successfully ran all of the unit tests on Mono 2.6.4 on Windows 7. It seems like there was the normal number of pass/fail results, but I would have to double check to be sure. However, the tests all did run. My final result numbers were: "Passed: 416, Failed: 26, Errors: 3, Time: 568.95"
I do notice that there are some visual drawing anomolies of the NUnit interface when running under Mono, and if I click on the Text Output tab, an error dialog pops up.
How are you running the tests, and what version of Mono are you using? I am also running the .NET 3.5 build of the tests.
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-263.
------------------------------
Resolution: Fixed
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60764#action_60764 ]
Timothy Bish commented on AMQNET-263:
-------------------------------------
Seems to be something I introduced, if you set the ActiveMQHost env var to an IP address it causes this, if its an machine name, or locahost, then the tests run. Weird.
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60713#action_60713 ]
Timothy Bish commented on AMQNET-263:
-------------------------------------
Under Mono NUnit 2.5.5 doesn't seem usable.
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-263.
---------------------------------
Resolution: Fixed
Fix in NMS.ActiveMQ trunk now allows me to run with an IP address set to the ENV var for the host.
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60762#action_60762 ]
Jim Gomes commented on AMQNET-263:
----------------------------------
I think you must be. I just successfully ran all of the unit tests on Mono 2.6.4 on Windows 7. It seems like there was the normal number of pass/fail results, but I would have to double check to be sure. However, the tests all did run. My final result numbers were: "Passed: 416, Failed: 26, Errors: 3, Time: 568.95"
I do notice that there are some visual drawing anomolies of the NUnit interface when running under Mono, and if I click on the Text Output tab, an error dialog pops up.
How are you running the tests, and what version of Mono are you using?
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60763#action_60763 ]
Timothy Bish commented on AMQNET-263:
-------------------------------------
This is what I see when I run the nant test target on my Windows XP 32bit VM instance.
{noformat}
set-net-2.0-framework-configuration:
[property] Target framework changed to "Microsoft .NET Framework 2.0".
[echo] Doing a signed debug build for the .NET 2.0 framework
dependency-init:
[exec] NUnit version 2.5.5.10112
[exec] Copyright (C) 2002-2009 Charlie Poole.
[exec] Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov.
[exec] Copyright (C) 2000-2002 Philip Craig.
[exec] All Rights Reserved.
[exec]
[exec] Runtime Environment -
[exec] OS Version: Microsoft Windows NT 5.1.2600 Service Pack 3
[exec] CLR Version: 2.0.50727.3607 ( Net 2.0 )
[exec]
[exec] ProcessModel: Default DomainUsage: Default
{noformat}
Bunch of tests......then
{noformat}
[exec]
[exec] Tests run: 445, Errors: 198, Failures: 2, Inconclusive: 0, Time: 99.342848 seconds
[exec] Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
[exec]
[exec] Errors and Failures:
[exec] 1) TearDown Error : Apache.NMS.ActiveMQ.Test.AMQQueueTransactionTest.AMQTransactionTestSupport.TestCloseConsumerBeforeCommit
[exec] System.UriFormatException : Invalid URI: The URI scheme is not valid.
[exec] TearDown : System.NullReferenceException : Object reference not set to an instance of an object.
[exec] at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
[exec] at System.Uri..ctor(String uriString)
[exec] at Apache.NMS.Util.URISupport.ParseComposite(Uri uri, CompositeData rc, String ssp) in c:\dev\NMS\src\main\csharp\Util\URISupport.
cs:line 463
[exec] at Apache.NMS.Util.URISupport.ParseComposite(Uri uri) in c:\dev\NMS\src\main\csharp\Util\URISupport.cs:line 415
[exec] at Apache.NMS.ActiveMQ.Connection.CreateSession(AcknowledgementMode sessionAcknowledgementMode) in c:\dev\NMS.ActiveMQ\src\main\cs
harp\Connection.cs:line 408
[exec] at Apache.NMS.ActiveMQ.Test.AMQTransactionTestSupport.ReconnectSession() in c:\dev\NMS.ActiveMQ\src\test\csharp\AMQTransactionTest
Support.cs:line 493
[exec] at Apache.NMS.ActiveMQ.Test.AMQTransactionTestSupport.Reconnect() in c:\dev\NMS.ActiveMQ\src\test\csharp\AMQTransactionTestSupport
.cs:line 482
[exec] at Apache.NMS.ActiveMQ.Test.AMQTransactionTestSupport.SetUp() in c:\dev\NMS.ActiveMQ\src\test\csharp\AMQTransactionTestSupport.cs:
line 54
[exec] --TearDown
[exec] at Apache.NMS.ActiveMQ.Test.AMQTransactionTestSupport.TearDown() in c:\dev\NMS.ActiveMQ\src\test\csharp\AMQTransactionTestSupport.
cs:line 60
{noformat}
This was working until the switch to 2.5.5 so not sure what's going on now, errors are about the same under Mono on Linux as well.
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work logged: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36922 ]
Jim Gomes logged work on AMQNET-263:
------------------------------------
Author: Jim Gomes
Created on: 16/Jul/10 06:10 PM
Start Date: 16/Jul/10 06:10 PM
Worklog Time Spent: 3 hours, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 hours)
Time Spent: 3 hours, 30 minutes
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reopened AMQNET-263:
---------------------------------
I must be missing something, no tests seem to pass even on Windows with .NET
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (AMQNET-263) Upgrade to NUnit 2.5.5
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60762#action_60762 ]
Jim Gomes edited comment on AMQNET-263 at 7/19/10 1:11 PM:
-----------------------------------------------------------
I think you must be. I just successfully ran all of the unit tests on Mono 2.6.4 on Windows 7. It seems like there was the normal number of pass/fail results, but I would have to double check to be sure. However, the tests all did run. My final result numbers were: "Passed: 416, Failed: 26, Errors: 3, Time: 568.95"
I do notice that there are some visual drawing anomolies of the NUnit interface when running under Mono, and if I click on the Text Output tab, an error dialog pops up.
How are you running the tests, and what version of Mono are you using? I am also running the .NET 3.5 build of the tests.
was (Author: semog):
I think you must be. I just successfully ran all of the unit tests on Mono 2.6.4 on Windows 7. It seems like there was the normal number of pass/fail results, but I would have to double check to be sure. However, the tests all did run. My final result numbers were: "Passed: 416, Failed: 26, Errors: 3, Time: 568.95"
I do notice that there are some visual drawing anomolies of the NUnit interface when running under Mono, and if I click on the Text Output tab, an error dialog pops up.
How are you running the tests, and what version of Mono are you using?
> Upgrade to NUnit 2.5.5
> ----------------------
>
> Key: AMQNET-263
> URL: https://issues.apache.org/activemq/browse/AMQNET-263
> Project: ActiveMQ .Net
> Issue Type: Test
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
> Affects Versions: 1.4.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Fix For: 1.4.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> Upgrade to the latest NUnit 2.5.5 libraries and APIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.