I was incorrect when I thought the problem had anything to do with Gallio. I wish I could rename the thread :) Thanks for those links, they will come in handy when we get ready to integrate the test reports produced by Gallio.
Take care, Leo On Apr 8, 11:17 am, Ruben Willems <[email protected]> wrote: > Hi > > I did just a quick google and found some things > > http://code.google.com/p/mb-unit/source/browse/trunk/v3/src/Extension...http://groups.google.com/group/gallio-dev/browse_thread/thread/259a69...http://www.gallio.org/Docs.aspxhttp://weblogs.asp.net/astopford/archive/2007/07/04/adding-mbunit-to-... > > hope this helps > > with kind regards > Ruben Willems > > On Thu, Apr 8, 2010 at 7:01 PM, Leo <[email protected]> wrote: > > I went through a lot of troubleshooting steps to figure out what could > > be happening. Here is a brief overview... > > > The build server is using XP and I am using Vista on my local machine. > > I went ahead and installed everything (cc.net, nant, etc) on my Vista > > machine to create a separate build environment where the only > > difference was the OS. On my vista machine everything worked as > > expected. > > > We determined that the errorlevel wasn't being handled properly on XP > > (no idea why). The build script is a batch file that calls out to Nant > > and it used a command EXIT /B %ERRORLEVEL% which I assume communicates > > the error code to the cc.net process that called the build.bat file. > > On the XP machine, removing the /B appears to fix the issue. > > > Without /B the command window exits when we are doing a local build. > > To resolve the issue, we created a LocalBuild.bat file that contains a > > single line "cmd /c build.bat" which keeps the command window open. > > > P.S. This had nothing to do with Gallio after all. I found builds that > > were failing (but reporting success) due to bad check-ins which didn't > > even get to execute the unit tests. > > > On Apr 7, 1:12 pm, Ruben Willems <[email protected]> wrote: > > > hi > > > > what is the return value of your batch file? > > > to check add the following > > > echo %errorlevel% > > > > a failed test should rerturn a non-zero number > > > > with kind regards > > > Ruben Willems > > > > On Wed, Apr 7, 2010 at 5:29 PM, Leo <[email protected]> wrote: > > > > Hi, > > > > > I'm using a batch file to run my build. When I run the build.bat file > > > > via command line, the build fails on unit tests. That is what I > > > > expect. However, when the automated build runs, the build shows up as > > > > passing even though the tests run by Gallio actually fail. I have the > > > > dashboard configured to show me the Gallio build report and indeed it > > > > shows all of the failed tests. I can't figure out why CC.Net is > > > > reporting a successful build. > > > > > Any help would be appreciated. > > > > > Take care, > > > > > Leo > > > > > -- > > > > To unsubscribe, reply using "remove me" as the subject. > >
