Created: (LOG4NET-114) Unit tests only support .NET 1.0

Unit tests only support .NET 1.0
--------------------------------

                 Key: LOG4NET-114
                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
             Project: Log4net
          Issue Type: Bug
          Components: Other
            Reporter: Curt Arnold


tests/nant.build only supports running the unit tests on
.NET 1.0, but supports compilation on .NET 1.1 and .NET 2.0.
 Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12474285 ] 

Curt Arnold commented on LOG4NET-114:
-------------------------------------

Rev 509338 will allow the unit tests to run (but fail) on
Mono 2.0.  Hopefully, doesn't make things worse on the
.NET's but has not been tested yet.

The contents of the compile-net-x.x targets appeared to be
identical (but could not confirm it).

The compile-mono-2.0 was copied from the compile-net-2.0 but
the nostdlib attribute was removed and the warnaserror
attribute was changed to false.  If nostdlib was present and
set to true, then undefined reference messages were
generated for framework types like System.Object.  If
warnaserror attribute was true, then compilation failed with
these warnings:

     [csc]
/Users/curta/ls-svn/log4net/tests/src/Layout/XmlLayoutTest.c
s(65,19): error CS0612:
`System.Xml.XmlConvert.ToString(System.DateTime)' is
obsolete
      [csc]
/Users/curta/ls-svn/log4net/tests/src/Layout/XmlLayoutTest.c
s(76,19): error CS0612:
`System.Xml.XmlConvert.ToString(System.DateTime)' is
obsolete


With the changes, the unit tests would run but 32 fail and 5
are not run.  Many of the changes appear to be due to
platform specific line ending characters.



> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12474325 ] 

Nicko Cadell commented on LOG4NET-114:
--------------------------------------

The main issue with running the unit tests from NAnt is that
the <nunit> task does not (last time I checked)
support multiple frameworks. That means that the NUnit tests
are run within the same .NET runtime as the NAnt process,
therefore you are limited to 1 framework, which in practice
is the default framework (highest version installed).

NAnt supports multiple frameworks for compilation by
executing a child process, on the required framework, to do
the compilation. In fact any NAnt task based on
ExternalProgramBase can make use of this.

To support running NAnt on multiple frameworks we would need
to build a new task that shells the NUnit process under the
required framework. This would allow us to run the unit
tests against all the build target frameworks.

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12474356 ] 

Curt Arnold commented on LOG4NET-114:
-------------------------------------

That could be an issue, but that was not the issue that I
was running up against.  As it was, the nant.build on Mono
would say that .NET 1.0, 1.1 and 2.0 were not present and
then exit without doing anything.  The modifications now
result in it saying that the 3 .NETs are not present and
then compile targeting the Mono framework and run the unit
tests.

As for targeting multiple frameworks, the nunit2 test
element supports an appconfig attribute.  If you compiled
the test with the earliest installed .NET or Mono framework,
then it seems you could run it with a different appconfig
file to force it to run on a later framework.

I think it likely that the compile-net-2.0 target will fail
with the same obsolete messages that the mono target
encountered.

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12474368 ] 

Gert Driesen commented on LOG4NET-114:
--------------------------------------

For now, I guess we should only run the tests again the
current runtime framework as this is what will happens
anyway.

I've considered added a new nunit task to NAnt(Contrib) that
would just be a wrapper around nunit-console. That way we
can at least support running tests on all versions of .NET
and Mono. Not sure if and how we can make run tests again
.NETCF or SSCLI.

The Spring.NET team took another approach and uses .NET
remoting. I haven't had time to look into that one though.

I'll probably start by adding nunit-console.exe to the NAnt
distribution, that way we can already modify the log4net
build script to use the <exec> task in order to run
the tests against the current target framework.



> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12475726 ] 

Nicko Cadell commented on LOG4NET-114:
--------------------------------------

I have changed the test build to run the tests for the
current framework only. This is the best we can do until
<nunit2> (or equivalent) supports multiple
frameworks.
I have also resolved the obsolete warning messages and other
warnings for the mono compile.

When I run the mono tests under mono 1.2.3 on windows XP I
get 5 failures, all from
log4net.Tests.Appender.RemotingAppenderTest, all with the
same error "Cannot create channel sink to connect to
URL". I will see if I can get a VM to run the mono
tests under linux.

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

     [ https://issues.apache.org/jira/browse/LOG4NET-114?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Curt Arnold updated LOG4NET-114:
--------------------------------

    Attachment: tests.log

Test results from Mono 1.2.3.1 on Mac OS/X.  In addition to
RemotingAppenderTest failures, other failures due to line
end conventions and a few other strays. 

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>         Attachments: tests.log
>
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse
/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12475793 ] 

Nicko Cadell commented on LOG4NET-114:
--------------------------------------

I have checked in an update to the tests that should fix the
line ending issues.

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>         Attachments: tests.log
>
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

     [ https://issues.apache.org/jira/browse/LOG4NET-114?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Curt Arnold updated LOG4NET-114:
--------------------------------

    Attachment: tests.log

Changes fixed all of the tests that displayed nr, but
causes some of the rolling file length mismatches to fail
differently.

> Unit tests only support .NET 1.0
> --------------------------------
>
>                 Key: LOG4NET-114
>                 URL: htt
ps://issues.apache.org/jira/browse/LOG4NET-114
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>            Reporter: Curt Arnold
>         Attachments: tests.log, tests.log
>
>
> tests/nant.build only supports running the unit tests
on .NET 1.0, but supports compilation on .NET 1.1 and .NET
2.0.  Mono is not supported for either test compilation or
running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.