Orchard 1.8 ClickToBuild nunit-console.exe error

Topics: Core, General
Aug 22, 2014 at 10:19 AM
I have just attempted to use the ClickToBuild on my new 1.8 Orchard project and I get this error when it hits the "test" part of the build
  Unhandled Exception: NUnit.Framework.AssertionException:   Expected: 1
    But was:  2

     at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)
     at Orchard.Tests.FileSystems.LockFile.LockFileManagerTests.PlayWithAcquire() in c:\Users\Ben\Documents\Team Foundation Server\Team Projects\Shar
  ed\Orchard 1.8 - Recruit Agent Web\src\Orchard.Tests\FileSystems\LockFile\LockFileManagerTests.cs:line 175
     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSync
  Ctx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
     at System.Threading.ThreadHelper.ThreadStart()
  .F.....F.F.F.F.F.F.F.F.F.F.F.F......F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F................................F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.
  F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.........N.....F.F.F.F.F.F.....N....F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F...............N.
  ...........................................F..F..F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F...............................
  .....................................................................F.F.F.F.F.F.F.F.N.F.F...........................................F.F.F.F...F.F.
  F...................F.F.F.F.F.F.F.F.F...................................................
C:\Users\Ben\Documents\Team Foundation Server\Team Projects\Shared\Orchard 1.8 - Recruit Agent Web\Orchard.proj(145,5): error MSB6006: "nunit-console
.exe" exited with code -532462766.
and at the bottom I am presented with this
  Unhandled Exception: NUnit.Framework.AssertionException:   Expected: 1
    But was:  2

     at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)
     at Orchard.Tests.FileSystems.LockFile.LockFileManagerTests.PlayWithAcquire() in c:\Users\Ben\Documents\Team Foundation Server\Team Projects\Shar
  ed\Orchard 1.8 - Recruit Agent Web\src\Orchard.Tests\FileSystems\LockFile\LockFileManagerTests.cs:line 175
     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSync
  Ctx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
     at System.Threading.ThreadHelper.ThreadStart()
  .F.....F.F.F.F.F.F.F.F.F.F.F.F......F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F................................F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.
  F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.........N.....F.F.F.F.F.F.....N....F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F...............N.
  ...........................................F..F..F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F.F...............................
  .....................................................................F.F.F.F.F.F.F.F.N.F.F...........................................F.F.F.F...F.F.
  F...................F.F.F.F.F.F.F.F.F...................................................
C:\Users\Ben\Documents\Team Foundation Server\Team Projects\Shared\Orchard 1.8 - Recruit Agent Web\Orchard.proj(145,5): error MSB6006: "nunit-console
.exe" exited with code -532462766.
Does this stop my project from building or is it ok for me to still publish to a server?
Aug 22, 2014 at 11:18 AM
I basically opened up my orchard.proj and commented out the nunit testing, this fixed it for me, but feel free to delete this topic or leave it just in case it helps others.
Coordinator
Aug 22, 2014 at 6:14 PM
We fixed it recently, it's a culture issue. I can assume you are not using an en-US locale.