Re: [Nant-dev] Good example of task unit tests
Troy Laurin wrote: Marcin, I don't have a link to good unit tests right now, but I do have some suggestions that unit tests should follow... Neither do I, but this happens to be an area in which I'm interested (specifically I'm interested both in automating Subversion and in unit testing), so I'd be glad to help work on these. the tests is not found. This will mark the tests as not run instead of failed, and so won't cause the build to fail. Personally, I think failed unit tests should never cause the build to fail unless they happen to be exploited as a gating mechanism for some other part of the build (e.g. an installation or deployment task). My definition of failure for a build is whether or not the explicit targets failed to meet their objectives. A build target fails if it didn't create all of the result files, a compile target fails if it couldn't create all of the .obj (or similar) files, a unit test target fails if it couldn't run the unit tests to produce a unit test result file (but not if the unit tests themselves produced failure), a clean target fails if anything is left around (but not if it couldn't clean because it was already clean), etc. I only mention this because I don't think NAnt's current mechanism for failure is up to this approach, so this may be food for thought for a future version. I'm thinking along the lines of explicit, detailed dependencies such as target a depends upon target b completing with any status, target c depends upon target d completing successfully, and target e depends upon target f running and failing. I think this is post v1.0, but it's an interesting idea. Gary --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Redesigned homepage
The wiki definitely has a place, in my opinion... I would just like to see it, at the very least, follow the same design/theme/style as the main NAnt site. That is, put the navigation tree and NAnt header on each wiki page. That way, navigating to and from the wiki is pretty easy... On Mon, 21 Mar 2005 10:07:21 +0800, Troy Laurin [EMAIL PROTECTED] wrote: On Sun, 20 Mar 2005 09:46:28 -0800, brant [EMAIL PROTECTED] wrote: Is there any reason why we don't just use the existing Wiki as the Default Home page; and build up the content from that? I'm not so sure this is a good idea. I think a wiki is an excellent collaboration device for support, because it can be updated easily and by any concerned party... but I think these features actually make it a *bad* match for a home page. This is where the official information regarding the project should be found. Of course, you could restrict edits to the official pages to the regular contributors, but then why are you using a wiki? In addition, if you look at the content of the menu in discussion, 90% is located in the release folder, which contains generated html pages and doesn't mesh well with the wiki world. Wiki sites are supposed to be structure-simple and content-rich. I think a project home page needs to be structure-rigid as well as content-rich. This doesn't mean that the wiki doesn't have a place, but it doesn't have to be the main home page to be a useful resource. -- Troy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1165252 ] copy task using created instead of modified date
Bugs item #1165252, was opened at 2005-03-17 08:10 Message generated for change (Comment added) made by swinslow You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1165252group_id=31650 Category: Tasks Group: 0.85 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Scott Winslow (swinslow) Assigned to: Gert Driesen (drieseng) Summary: copy task using created instead of modified date Initial Comment: copy is overwriting newer files with older files because it checks age based on created date rather than modified date. I'm pretty sure that it should be modified date, otherwise simply relocating a file prior to the copy task will make the file look newer than it really is. As an example: if you create a file, copy it elsewhere and then go back and modify the original, copy would not overwrite the previously copied file with the more recently modified one. Considering that the touch task is touching the modified date, I think that copy's use of the created date is a bug rather than the intended behaviour. File in directory: Created:Monday, March 14, 2005, 7:31:44 PM Modified: Monday, March 14, 2005, 7:31:35 PM Accessed: Today, March 16, 2005, 11:12:36 AM File overwriting it: Created:Today, March 16, 2005, 11:23:44 AM Modified: Monday, March 07, 2005, 12:16:11 PM Accessed: Today, March 16, 2005, 11:23:44 AM NAnt 0.85 (Build 0.85.1793.0; rc1; 11/28/2004) Framework version 1.1.4322 OS Version: Win2000 Server 5.00.2195 SP4 -- Comment By: Scott Winslow (swinslow) Date: 2005-03-21 10:22 Message: Logged In: YES user_id=86359 You're test file worked fine, but I've attached one that shows what I was seeing. Sorry for not giving more info the first time around: I'm copying multiple project outputs into a single directory, and there is overlap because one of these projects is a collection of foundation DLLs we use in all other projects. I want to make sure I get the most recently compiled of each DLL without having to know the order the projects were most recently built in. Based on copy's documentation, it looked like running it with flatten=true was going to do exactly what I wanted. Whether it's due to the flatten operation or something to do with the file names matching, it doesn't seem to be acting right in my scenario. I did a quick peek at the source, and where I looked it was using the modified date, so I'm rather confused as well... -- Comment By: Gert Driesen (drieseng) Date: 2005-03-18 11:34 Message: Logged In: YES user_id=707851 Scott, We're definitely using the last write time (modified date) to check whether a certain is up-to-date. I've attached a build file that I used to try to reproduce this issue. Let me know if you get the same results using that build file. Gert -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1165252group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1167694 ] solution task is not detecting compile errors in resgen
Bugs item #1167694, was opened at 2005-03-21 16:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: John Hardin (john_hardin)
Assigned to: Nobody/Anonymous (nobody)
Summary: solution task is not detecting compile errors in resgen
Initial Comment:
One of our ccnet-managed automatic builds was failing.
The error message was somewhat misleading, and further
investigation suggests that nant 0.85rc2 is not
detecting compile errors in a solution task under
certain circumstances.
Here is an excerpt of the solution's XML log,
building the CRM subproject:
message level=InfoBuilding 'CRM' [debug] .../message
task name=attrib/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(18,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or
namespace 'CRS.VisualFramework.WinForms' (are you
missing an assembly reference?)
/message
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(19,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or namespace
'CRS.VisualFramework.WinForms' (are you missing an ssembly
reference?)
/message
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=delete/
Note that the compile errors did NOT generate a failed
build. The build failed later in ndoc when the
documentation .xml for the CRM project couldn't be found.
The only odd thing I can see is that the errors appear
to be during resgen tasks.
The above is about all the information I can provide -
the errors in our code have been fixed, and I don't
know what to do to provide a minimal repro.
Sorry.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1167694 ] solution task is not detecting compile errors in resgen
Bugs item #1167694, was opened at 2005-03-21 16:26
Message generated for change (Comment added) made by john_hardin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: John Hardin (john_hardin)
Assigned to: Nobody/Anonymous (nobody)
Summary: solution task is not detecting compile errors in resgen
Initial Comment:
One of our ccnet-managed automatic builds was failing.
The error message was somewhat misleading, and further
investigation suggests that nant 0.85rc2 is not
detecting compile errors in a solution task under
certain circumstances.
Here is an excerpt of the solution's XML log,
building the CRM subproject:
message level=InfoBuilding 'CRM' [debug] .../message
task name=attrib/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(18,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or
namespace 'CRS.VisualFramework.WinForms' (are you
missing an assembly reference?)
/message
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(19,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or namespace
'CRS.VisualFramework.WinForms' (are you missing an ssembly
reference?)
/message
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=delete/
Note that the compile errors did NOT generate a failed
build. The build failed later in ndoc when the
documentation .xml for the CRM project couldn't be found.
The only odd thing I can see is that the errors appear
to be during resgen tasks.
The above is about all the information I can provide -
the errors in our code have been fixed, and I don't
know what to do to provide a minimal repro.
Sorry.
--
Comment By: John Hardin (john_hardin)
Date: 2005-03-21 23:30
Message:
Logged In: YES
user_id=786519
The build file is pretty big. The part where the solution
task lives is dirt simple:
property name=nant.settings.currentframework
value=net-1.1/
solution configuration=debug
solutionfile=${project::get-name()}.sln /
...as you can see, failonerror is not being set to false.
The build file is common across multiple projects - they
just set the project name and include it. The build process
works properly on all projects except the one doing user
interface stuff, and only when the control developers change
things that break other bits of the UI.
I am not closely involved with that side of things so I
don't know how to approach making a minimal repro example
for this, and I don't know whether the UI people will be
able to make a minimal repro example either. I'll ask.
Is there a more verbose level of nant debug logging I can
enable that will help track down what's wrong? I think I can
get the UI devs to break the build without too much
trouble... :)
--
Comment By: Gert Driesen (drieseng)
Date: 2005-03-21 21:52
Message:
Logged In: YES
user_id=707851
John,
Can you attach your build file to this bug report ?
Are you sure that you don't have failonerror set to false on
the solution task ?
The error messages are not output by resgen, but by csc. Its
just not obvious as we don't use the csc task, but instead
execute csc.exe directly.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Redesigned homepage
Troy Laurin wrote: On Sun, 20 Mar 2005 09:46:28 -0800, brant [EMAIL PROTECTED] wrote: Is there any reason why we don't just use the existing Wiki as the Default Home page; and build up the content from that? I'm not so sure this is a good idea. I think a wiki is an excellent collaboration device for support, because it can be updated easily and by any concerned party... but I think these features actually make it a *bad* match for a home page. This is where the official information regarding the project should be found. Of course, you could restrict edits to the official pages to the regular contributors, but then why are you using a wiki? I quite agree. Wikis also result in navigation structures that shout this was designed by committee, i.e. not at all. Sometimes they're useful, but more often they turn into black holes of time-consuming, interesting discussions that don't answer the question. Wiki sites are supposed to be structure-simple and content-rich. I think a project home page needs to be structure-rigid as well as content-rich. This doesn't mean that the wiki doesn't have a place, but it doesn't have to be the main home page to be a useful resource. I think you've hit the nail on the head with both these paragraphs. Gary --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1167694 ] solution task is not detecting compile errors in resgen
Bugs item #1167694, was opened at 2005-03-21 17:26
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: John Hardin (john_hardin)
Assigned to: Nobody/Anonymous (nobody)
Summary: solution task is not detecting compile errors in resgen
Initial Comment:
One of our ccnet-managed automatic builds was failing.
The error message was somewhat misleading, and further
investigation suggests that nant 0.85rc2 is not
detecting compile errors in a solution task under
certain circumstances.
Here is an excerpt of the solution's XML log,
building the CRM subproject:
message level=InfoBuilding 'CRM' [debug] .../message
task name=attrib/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
task name=resgen/
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(18,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or
namespace 'CRS.VisualFramework.WinForms' (are you
missing an assembly reference?)
/message
message level=Info
c:\{mumble}\CRM\CreateNotesForm.cs(19,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or namespace
'CRS.VisualFramework.WinForms' (are you missing an ssembly
reference?)
/message
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=copy/
task name=delete/
Note that the compile errors did NOT generate a failed
build. The build failed later in ndoc when the
documentation .xml for the CRM project couldn't be found.
The only odd thing I can see is that the errors appear
to be during resgen tasks.
The above is about all the information I can provide -
the errors in our code have been fixed, and I don't
know what to do to provide a minimal repro.
Sorry.
--
Comment By: Gert Driesen (drieseng)
Date: 2005-03-22 07:16
Message:
Logged In: YES
user_id=707851
You can run the build in debug mode:
NAnt.exe -debug -logger:NAnt.Core.XmlLogger -
logfile:log.xml -buildfile:your buildfile
--
Comment By: John Hardin (john_hardin)
Date: 2005-03-22 00:30
Message:
Logged In: YES
user_id=786519
The build file is pretty big. The part where the solution
task lives is dirt simple:
property name=nant.settings.currentframework
value=net-1.1/
solution configuration=debug
solutionfile=${project::get-name()}.sln /
...as you can see, failonerror is not being set to false.
The build file is common across multiple projects - they
just set the project name and include it. The build process
works properly on all projects except the one doing user
interface stuff, and only when the control developers change
things that break other bits of the UI.
I am not closely involved with that side of things so I
don't know how to approach making a minimal repro example
for this, and I don't know whether the UI people will be
able to make a minimal repro example either. I'll ask.
Is there a more verbose level of nant debug logging I can
enable that will help track down what's wrong? I think I can
get the UI devs to break the build without too much
trouble... :)
--
Comment By: Gert Driesen (drieseng)
Date: 2005-03-21 22:52
Message:
Logged In: YES
user_id=707851
John,
Can you attach your build file to this bug report ?
Are you sure that you don't have failonerror set to false on
the solution task ?
The error messages are not output by resgen, but by csc. Its
just not obvious as we don't use the csc task, but instead
execute csc.exe directly.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1167694group_id=31650
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
