[nant-dev] Nant tests
Title: Message Hi. I've take my time now to test nightly 11-15 and as far as I can tell it's doing it's job just fine. I'm compiling a lot of C# projects some of them are pretty large. No satellite assemblies or any other advanced stuff. Also got quite a bit of other extra code for tests, clean FxCop etc. All seem to work equally well as 11-08 that we have in production. Performance doesn't seem to be any worse or better then 11-08 (not clocked). Take it for what it's worth... /Nicke
[nant-dev] NAnt tests, the csproj files and the sln files in CVS
Recently got yet-another fresh checkout from CVS and ran into a few problems which then raises a few questions The root .build file successfully compiles everything, but the unit tests dont make it. Now that Im typing this, that behavior strikes me as even stranger, because when building from the .sln file, the tests project wont compile not just because of munged references settings to nunit and nant.core, but some of the tests reference a non-existent default constructor for Project. (getTask.Project = new Project();) So my questions: 1) Am I fat-fingering something, or is the .build file not currently capable of firing off successfully? 2) Ditto for the .sln file. 3) What is, or is there, a philosophy regarding the build and sln file? Ive noticed they seem to float near- each other in terms of how and what they build, but not usually identically. I assume the .build file is the official version, as that is what Draco.Net is using, yes? Wouldnt it be a Good Thing to keep the sln and .build functionally identical? 4) Anyone I should ping or any gotchas I should know before I just start submitting patches on this? TTFN, Brian (and Ian, I thought you were gonna commit my vast improvement on the echo task?) J
Re: [nant-dev] NAnt tests, the csproj files and the sln files in CVS
Brian, The VS.Net files are just there for editing (and debugging). I try to keep them in sync with the build files, but they are not thereto build the project. The nightly builds runfrom the "nightly.build" filevia Draco.Netfroma new anon cvscheckout. It basically runs a full release build, tests, docs and zips everything up. If people are interested I can have the nightly builds send email to the cvs-commit list so everyone can see it. Or we can even setup a new list just for this purpose, but that seems overkill. Feel free to submit patches. The tests were not compiled because of NUnit diffs from the past(and the fact that you can not ref a exe--not an issue anymore). I thinkthat VS.Net should be able to build things in a very similar manner to the main buildfile. But I never felt that it had to as it will never be the"correct" way to build NAnt. Note:See the build file because some of the tests are not compiled/used. HTH, Scott - Original Message - From: Brian Deacon To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 9:24 AM Subject: [nant-dev] NAnt tests, the csproj files and the sln files in CVS Recently got yet-another fresh checkout from CVS and ran into a few problems which then raises a few questions The root .build file successfully compiles everything, but the unit tests dont make it. Now that Im typing this, that behavior strikes me as even stranger, because when building from the .sln file, the tests project wont compile not just because of munged references settings to nunit and nant.core, but some of the tests reference a non-existent default constructor for Project. (getTask.Project = new Project();) So my questions: 1) Am I fat-fingering something, or is the .build file not currently capable of firing off successfully? 2) Ditto for the .sln file. 3) What is, or is there, a philosophy regarding the build and sln file? Ive noticed they seem to float near- each other in terms of how and what they build, but not usually identically. I assume the .build file is the official version, as that is what Draco.Net is using, yes? Wouldnt it be a Good Thing to keep the sln and .build functionally identical? 4) Anyone I should ping or any gotchas I should know before I just start submitting patches on this? TTFN, Brian (and Ian, I thought you were gonna commit my vast improvement on the echo task?) J
RE: [nant-dev] NAnt tests, the csproj files and the sln files in CVS
Thanks, Scott Ill dig into the metabuild and get myself sorted. I can assume then that Draco isnt getting what Im getting, then? (This is with nant package, but Im getting the same with the default in debug.) test: [echo] Running unit tests with just built version of NAnt. [exec] C:\CVSRoot\nant/build/nant-0.8.01/bin/NAnt.exe -indent:1 -buildfile :NAnt.build release self-test -D:project.version=0.8.01 Buildfile: file:///C:/CVSRoot/nant/NAnt.build release: init: self-test: [echo] c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\new.txt is newer than c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\old.txt Tests run: 105, Failures: 1, Not run: 0, Time: 5.0625 seconds Failures: 1) SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal : c:\cvsroot\nant\SourceFor ge.NAnt.Tests.AttribTaskTest\myfile.txt should have Normal file attribute. at SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal() Id be +1 on sending nant.onfailure to cvs-commit but agree that much more than that is overkill. -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 9:47 AM To: Brian Deacon Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] NAnt tests, the csproj files and the sln files in CVS Brian, The VS.Net files are just there for editing (and debugging). I try to keep them in sync with the build files, but they are not thereto build the project. The nightly builds runfrom the nightly.build filevia Draco.Netfroma new anon cvscheckout. It basically runs a full release build, tests, docs and zips everything up. If people are interested I can have the nightly builds send email to the cvs-commit list so everyone can see it. Or we can even setup a new list just for this purpose, but that seems overkill. Feel free to submit patches. The tests were not compiled because of NUnit diffs from the past(and the fact that you can not ref a exe--not an issue anymore). I thinkthat VS.Net should be able to build things in a very similar manner to the main buildfile. But I never felt that it had to as it will never be thecorrect way to build NAnt. Note:See the build file because some of the tests are not compiled/used. HTH, Scott - Original Message - From: Brian Deacon To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 9:24 AM Subject: [nant-dev] NAnt tests, the csproj files and the sln files in CVS Recently got yet-another fresh checkout from CVS and ran into a few problems which then raises a few questions The root .build file successfully compiles everything, but the unit tests dont make it. Now that Im typing this, that behavior strikes me as even stranger, because when building from the .sln file, the tests project wont compile not just because of munged references settings to nunit and nant.core, but some of the tests reference a non-existent default constructor for Project. (getTask.Project = new Project();) So my questions: 1. Am I fat-fingering something, or is the .build file not currently capable of firing off successfully? 2. Ditto for the .sln file. 3. What is, or is there, a philosophy regarding the build and sln file? Ive noticed they seem to float near- each other in terms of how and what they build, but not usually identically. I assume the .build file is the official version, as that is what Draco.Net is using, yes? Wouldnt it be a Good Thing to keep the sln and .build functionally identical? 4. Anyone I should ping or any gotchas I should know before I just start submitting patches on this? TTFN, Brian (and Ian, I thought you were gonna commit my vast improvement on the echo task?) J
Re: [nant-dev] NAnt tests, the csproj files and the sln files in CVS
Yeah, I've seen this (time/date
failures)posted before. It doesn't show up in my builds, or the nightly
one, but people are seeing it consistently. If you can track this done it would
be very helpful :)
On a related note, we really need to beef up the
unit tests. That is definitely something that would be a great contribution by
anyone.
- Original Message -
From:
Brian Deacon
To: 'Scott Hernandez'
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 2:06
PM
Subject: RE: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
Thanks, Scott
Ill
dig into the metabuild and get myself
sorted.
I can assume then
that Draco isnt getting what Im getting,
then? (This is with nant package, but Im getting the same with the default
in debug.)
test:
[echo] Running unit tests with just built version of NAnt.
[exec] C:\CVSRoot\nant/build/nant-0.8.01/bin/NAnt.exe
-indent:1 -buildfile
:NAnt.build release
self-test -D:project.version=0.8.01
Buildfile:
file:///C:/CVSRoot/nant/NAnt.build
release:
init:
self-test:
[echo]
c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\new.txt
is
newer than
c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\old.txt
Tests run: 105, Failures: 1, Not run: 0, Time: 5.0625
seconds
Failures:
1) SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal :
c:\cvsroot\nant\SourceFor
ge.NAnt.Tests.AttribTaskTest\myfile.txt
should have Normal file
attribute.
at
SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal()
Id be +1 on sending
nant.onfailure to cvs-commit
but agree that much more than that is
overkill.
-Original
Message-From: Scott
Hernandez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19,
2003 9:47
AMTo: Brian DeaconCc:
[EMAIL PROTECTED]Subject: Re: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
Brian,
The VS.Net files are just there
for editing (and debugging). I try to keep them in sync with the build files,
but they are not thereto build the
project.
The nightly builds runfrom
the "nightly.build" filevia Draco.Netfroma new anon
cvscheckout. It basically runs a full release build, tests, docs and
zips everything up. If people are interested I can have the nightly builds
send email to the cvs-commit list so everyone can see it. Or we can even setup
a new list just for this purpose, but that seems
overkill.
Feel free to submit patches. The
tests were not compiled because of NUnit diffs from the past(and the fact that
you can not ref a exe--not an issue anymore). I thinkthat VS.Net should
be able to build things in a very similar manner to the main buildfile. But I
never felt that it had to as it will never be the"correct" way to build
NAnt.
Note:See the build file
because some of the tests are not
compiled/used.
HTH,
Scott
- Original Message -
From: Brian Deacon
To: [EMAIL PROTECTED]
Sent:
Wednesday, February
19, 2003 9:24
AM
Subject:
[nant-dev] NAnt tests, the csproj files and the sln files in
CVS
Recently got yet-another fresh
checkout from CVS and ran into a few problems
which then raises a few
questions
The root .build file
successfully compiles everything, but the unit tests dont make it. Now that Im typing this, that
behavior strikes me as even stranger, because when building from the .sln
file, the tests project wont compile not just because of munged references
settings to nunit and nant.core, but some of the tests reference a
non-existent default constructor for Project. (getTask.Project = new
Project();)
So my
questions:
1. Am I fat-fingering
something, or is the .build file not currently capable of firing off
successfully?
2. Ditto for the .sln
file.
3. What is, or is
there, a philosophy regarding the build and sln file? Ive noticed they seem to float
near- each other in terms of how and what they build, but not usually
identically. I assume the
.build file is the official version, as that is what Draco.Net is using,
yes? Wouldnt it be a Good
Thing to keep the sln and .build functionally
identical?
4. Anyone I should
ping or any gotchas I should know before I just start submitting patches on
this?
TTFN,
Brian
(and Ian, I thought you were
gonna commit my vast improvement on the echo
task?)
J
Re: [nant-dev] NAnt tests, the csproj files and the sln files in CVS
Okay, I apparently lied. I can in-fact see this in
my builds. I took off my special blinders. :)
I just ran the nightly build (but it isn't night
you say, yeah... yeah) to check for this message. I've setup the nightly build
(which will only occur if there were changes since the last nightly build) to
email the cvs-commits list. So now you can see the status of our nightly
builds.
- Original Message -
From:
Scott Hernandez
To: Brian Deacon
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 3:00
PM
Subject: Re: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
Yeah, I've seen this (time/date
failures)posted before. It doesn't show up in my builds, or the nightly
one, but people are seeing it consistently. If you can track this done it
would be very helpful :)
On a related note, we really need to beef up the
unit tests. That is definitely something that would be a great contribution by
anyone.
- Original Message -
From:
Brian Deacon
To: 'Scott Hernandez'
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 2:06
PM
Subject: RE: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
Thanks, Scott
Ill
dig into the metabuild and get myself
sorted.
I can assume then
that Draco isnt getting what Im getting,
then? (This is with nant package, but Im getting the same with the default
in debug.)
test:
[echo] Running unit tests with just built version of NAnt.
[exec] C:\CVSRoot\nant/build/nant-0.8.01/bin/NAnt.exe
-indent:1 -buildfile
:NAnt.build release self-test
-D:project.version=0.8.01
Buildfile:
file:///C:/CVSRoot/nant/NAnt.build
release:
init:
self-test:
[echo]
c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\new.txt
is
newer than
c:\cvsroot\nant\SourceForge.NAnt.Tests.IfTest\old.txt
Tests run: 105, Failures: 1, Not run: 0, Time: 5.0625
seconds
Failures:
1) SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal :
c:\cvsroot\nant\SourceFor
ge.NAnt.Tests.AttribTaskTest\myfile.txt
should have Normal file
attribute.
at
SourceForge.NAnt.Tests.AttribTaskTest.Test_Normal()
Id be +1 on
sending nant.onfailure to cvs-commit
but agree that much more than that is
overkill.
-Original
Message-From: Scott
Hernandez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19,
2003 9:47
AMTo: Brian DeaconCc:
[EMAIL PROTECTED]Subject: Re: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
Brian,
The VS.Net files are just there
for editing (and debugging). I try to keep them in sync with the build
files, but they are not thereto build the
project.
The nightly builds runfrom
the "nightly.build" filevia Draco.Netfroma new anon
cvscheckout. It basically runs a full release build, tests, docs and
zips everything up. If people are interested I can have the nightly builds
send email to the cvs-commit list so everyone can see it. Or we can even
setup a new list just for this purpose, but that seems
overkill.
Feel free to submit patches. The
tests were not compiled because of NUnit diffs from the past(and the fact
that you can not ref a exe--not an issue anymore). I thinkthat VS.Net
should be able to build things in a very similar manner to the main
buildfile. But I never felt that it had to as it will never be
the"correct" way to build NAnt.
Note:See the build file
because some of the tests are not
compiled/used.
HTH,
Scott
- Original Message -
From: Brian Deacon
To: [EMAIL PROTECTED]
Sent:
Wednesday,
February 19, 2003 9:24
AM
Subject:
[nant-dev] NAnt tests, the csproj files and the sln files in
CVS
Recently got
yet-another fresh checkout from CVS and ran into a few problems
which
then raises a few questions
The root .build
file successfully compiles everything, but the unit tests dont make
it. Now that Im typing this,
that behavior strikes me as even stranger, because when building from the
.sln file, the tests project wont compile not just because of munged
references settings to nunit and nant.core, but some of the tests
reference a non-existent default constructor for Project. (getTask.Project = new
Project();)
So my
questions:
1. Am I
fat-fingering something, o
Re: [nant-dev] NAnt tests, the csproj files and the sln files inCVS
Brian Deacon wrote: (and Ian, I thought you were gonna commit my vast improvement on the echo task?) Committed ! thanks. Ian --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
