- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 5:28 AM
Subject: [nant-dev] current cvs build failure
> A fresh cvs checkout of nant is failing with the following :
>
> [echo] Running unit
A fresh cvs checkout of nant is failing with the following :
[echo] Running unit tests with just built version of NAnt.
[exec]
H:\cvs\nant-test\nant/build/net-1.1.win32/nant-0.85-debug/bin/NAnt.exe
-buildfile:NAnt.build debug self-test -D:proje
ct.version=0.85 -targetframework:net-1.1
Matthew Mastracci wrote:
Here's a few hot-spots that someone could probably pick off pretty
easy. All percentages are relative to total time.
This is from running a task based build. I haven't tried a
-based build yet.
ProjectSettingsLoader::ProcessPlatform -> 5.6%
+- ProjectSettingsLoader:
It looks like the regex optimization broke an edge case:
**/* now matches the base directory, as well as any subdirectories on a
FileSet.DirectoryNames call. For instance, in the following directory
structure, all three will be matched with a base directory of "C:\foo":
C:\foo
C:\foo\bar
C:\foo
Okay, compiling all regexes makes the Regex.Test() contribution now 30%
of the total runtime, versus 60% before. :)
Surprisingly, the compilation of the regexes seems to be negligible
(something I didn't expect). Checked-in.
Next, I optimized some of our common regexes:
1. **/blah/** was bei
Here's a few hot-spots that someone could probably pick off pretty easy.
All percentages are relative to total time.
This is from running a task based build. I haven't tried a
-based build yet.
ProjectSettingsLoader::ProcessPlatform -> 5.6%
+- ProjectSettingsLoader::ProcessFrameworks -> 2%
