Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
3 Pages<123
Projects won't build
Options
Previous Topic Next Topic
DanHil
#41 Posted : Wednesday, December 5, 2012 10:36:26 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Remco;3357 wrote:
When you say that the directory was missing, do you mean the SalesQuotasViewModelTest directory, or the entire workspace?

Sorry, I can't answer that. I assume, the folder 330 was missing as this was the case with the missing xunit.dll but I can't say for sure as I haven't checked that in depth. I could check tomorrow at work, but I don't know if this will help as I have since resetted NCrunch.
Back to top
Remco
#42 Posted : Wednesday, December 5, 2012 10:41:34 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks. The 330 folder is the workspace root, so this would suggest the entire workspace is gone.

I think I may have found a rare race condition that can cause this situation. I'll look into this deeper and will update you if I find anything.
Back to top
DanHil
#43 Posted : Thursday, December 6, 2012 11:15:44 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I just checked: The folder 330 is indeed missing.
Maybe you can extract any information from the existing and missing workspace folders:

Quote:
04.12.2012 17:59 <DIR> 154
04.12.2012 18:01 <DIR> 158
04.12.2012 17:59 <DIR> 159
04.12.2012 18:04 <DIR> 169
05.12.2012 10:57 <DIR> 209
05.12.2012 10:58 <DIR> 230
05.12.2012 15:54 <DIR> 272
05.12.2012 15:59 <DIR> 285
05.12.2012 16:26 <DIR> 306
05.12.2012 17:12 <DIR> 323
05.12.2012 17:22 <DIR> 324
05.12.2012 17:31 <DIR> 333
05.12.2012 17:34 <DIR> 334
05.12.2012 17:34 <DIR> 335
05.12.2012 17:34 <DIR> 336
05.12.2012 17:34 <DIR> 337
05.12.2012 17:34 <DIR> 338
05.12.2012 17:34 <DIR> 339
05.12.2012 18:01 <DIR> 340
05.12.2012 17:34 <DIR> 341
05.12.2012 17:34 <DIR> 342
05.12.2012 17:34 <DIR> 343
05.12.2012 17:34 <DIR> 344
05.12.2012 17:34 <DIR> 346
05.12.2012 17:34 <DIR> 347
05.12.2012 17:34 <DIR> 348
05.12.2012 17:34 <DIR> 349
05.12.2012 17:39 <DIR> 350
05.12.2012 17:40 <DIR> 351
05.12.2012 17:40 <DIR> 352
05.12.2012 17:40 <DIR> 353
05.12.2012 17:45 <DIR> 354
05.12.2012 17:40 <DIR> 355
05.12.2012 17:40 <DIR> 356
05.12.2012 17:40 <DIR> 357
05.12.2012 17:40 <DIR> 359
05.12.2012 17:48 <DIR> 363
05.12.2012 17:58 <DIR> 367
04.12.2012 16:20 <DIR> 37
05.12.2012 17:59 <DIR> 370
05.12.2012 17:59 <DIR> 371
05.12.2012 17:57 <DIR> 375
05.12.2012 17:59 <DIR> 376
05.12.2012 18:01 <DIR> 377
04.12.2012 16:20 <DIR> 58
04.12.2012 16:27 <DIR> 69
04.12.2012 16:27 <DIR> 70
04.12.2012 16:59 <DIR> 73
04.12.2012 16:53 <DIR> 74
04.12.2012 17:51 <DIR> 84
Back to top
 |  Edit by user
DanHil
#44 Posted : Thursday, December 6, 2012 3:51:07 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
It happened again:

Quote:
[16:45:50.5788-BuildTask-168] ERROR (Internal): System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\daniel.hilgarth\AppData\Local\NCrunch\16368\84\GA.CoreData.UnitTests\SalesQuotas\SalesQuotasViewModelTest\ShownWeeks.cs'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at nCrunch.Core.ProjectItems.SnapshotComponentMember.#=qRXf4UTRNcH1z5jIylzMoCAnFb2Tcmmdfhm21$Uud1PE=(String #=qIDcl4VGF5QsNDCrrEFo01w==)
at nCrunch.Core.ProjectItems.SnapshotComponentMember.WriteToFile(String fileToWriteTo)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.#=quyOMvjuRjJLlg$bsXV0j8WyvVbLWOkwSAug9mW9bjTY=(SnapshotComponent #=qDCuRCNUMnw5lOdfyM$WBrQ==, Workspace #=qjHvwLlb3x$Zum_vmRr9nrg==)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.UpdateExistingWorkspaceForComponent(SnapshotComponent component, Workspace& workspace)
at nCrunch.Core.WorkspaceManagement.WorkspaceManager.GetWorkspaceForComponent(SnapshotComponent snapshotComponent)
at nCrunch.Core.BuildManagement.BuildEnvironment.Build(SnapshotComponent snapshotComponentToBuild, IList`1 referencedComponents)
at nCrunch.Core.BuildTask.DoProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingTask.ProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingQueue.#=qmw8TP7OZQi1Awa12Usj2mw==(ProcessingTask #=qbasxLAEC$whviXkzL8WKzA==)


This time I verified that the complete workspace is missing, there is no folder 84.

The file ShownWeeks.cs is again a file I have added a few minutes earlier. After that NCrunch executed the test in that file for a few minutes before the above error occurred.
Back to top
Remco
#45 Posted : Friday, December 7, 2012 12:40:22 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Dan,

I've prepared a build for you to help with troubleshooting this problem:

http://downloads.ncrunch.net/NCrunch_VS2012_1.43.0.21.msi
http://downloads.ncrunch.net/NCrunch_VS2010_1.43.0.21.msi

This is essentially an early build of the 1.43 release that I'm hoping to push out next week, as such, it contains a number of other fixes and optimisations that you may find useful. In an effort to resolve the problem you've reported above, this build contains a change to help strengthen some of the workspace handling.

I've also increased the captured log file to 10 times its normal size, as you've been reporting a large number of intermittent problems that appear to be symptoms of something going wrong much further in advance (and out of range of the normal bug report logs). You may notice a slight increase in memory consumption as a result of the extra logging, and any reports you capture will be significantly larger.

My hope is that this build will solve the problem you've described above, or at the very least will provide me with more information in order to reproduce and resolve it.


Cheers,

Remco
Back to top
DanHil
#46 Posted : Friday, December 7, 2012 9:54:26 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Thanks for the build. However, I fear we have a little problem here. My trial will expire in two days and version 1.42 was too fragile for me, as you surely noticed. It actually cost me more time than it saved, so to be honest, I am not yet prepared to pay for a license.
Furthermore, next week will be the last week before three weeks of christmas holiday [yeah! :-)], so even if you would be willing to extend the trial phase by another 30 days it would gain us only one additional week of testing.
Back to top
 |  Edit by user
DanHil
#47 Posted : Friday, December 7, 2012 11:50:48 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
The new version doesn't recognize my xunit tests anymore. Any ideas?
Back to top
DanHil
#48 Posted : Friday, December 7, 2012 12:01:32 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Hm, I guess I know why: xunit.dll and xunit.extensions.dll were missing in c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010\Xunit\Latest\.

Adding them brought my xunit tests back.
Back to top
DanHil
#49 Posted : Friday, December 7, 2012 12:25:13 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
In the new version, the stack traces of failed tests no longer contain links on which I can click to navigate to the offending line.
Back to top
Remco
#50 Posted : Friday, December 7, 2012 10:40:54 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
1.43 contains a modification that disables navigation to source files that exist within the NCrunch workspace. Are the links themselves pointing to files within workspaces, or to your foreground solution? If they're pointing at the workspace, this is intended behaviour .. if they point at the foreground solution and they don't work, then this is definitely a bug.

Regarding the Xunit issue, did you at any time update your xunit binaries while using the previous version?

I'm sorry about the problems you've experienced with 1.42. I hope you have a great Christmas break and I wish you all the best.


Cheers,

Remco
Back to top
DanHil
#51 Posted : Sunday, December 9, 2012 8:48:31 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Remco;3378 wrote:
1.43 contains a modification that disables navigation to source files that exist within the NCrunch workspace. Are the links themselves pointing to files within workspaces, or to your foreground solution? If they're pointing at the workspace, this is intended behaviour .. if they point at the foreground solution and they don't work, then this is definitely a bug.

I saw that thread regarding this and checked the paths in detail. They were pointing to my solution, not to the NCrunch workspace.

Remco;3378 wrote:
Regarding the Xunit issue, did you at any time update your xunit binaries while using the previous version?

I did.
Back to top
Remco
#52 Posted : Monday, December 10, 2012 4:41:40 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for sharing the navigation issue. It looks as though one of the changes in the 1.43 release introduced a regression here. I've included a fix for this in the full 1.43 release that just went out the door (available on the download page).

I have a feeling that updating the xunit binaries in your NCrunch installation caused the MSI installer to fall out of alignment and create a problem here. I think the best way to resolve this is to follow the uninstall/reinstall instructions to create a clean setup, as simply placing the binaries back in manually will likely cause this problem to happen again the next time you upgrade.
Back to top
Users browsing this topic
Guest
3 Pages<123
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.092 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download