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

Notification

Icon
Error

Stuck at "ncrunch engine is initialising"
koraybalci
#1 Posted : Monday, February 21, 2022 5:45:58 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/6/2019(UTC)
Posts: 5
Location: Australia

Thanks: 3 times
Hi there,

I have upgraded my Microsoft Visual Studio Professional 2022 (64-bit) - Preview to Version 17.2.0 Preview 1.0 recently.

Now, all the solutions are stuck at "NCrunch engine is initialising" message. N at bottom right is spinning around in blue forever and no projects or tests are found. I am not sure if it's related to above upgrade entirely though.

The issue is happening in multiple solutions (all dotnet core).

I am not sure if I can post a screenshot, but, my NCrunch Tests pane is essentially empty.

I tried restarting VStudio and PC as well as triggering restarting the NCrunch engine and running the NCrunch wizard.

I will also submit an NCrunch bug report with the same title as this thread, so that you can perhaps see some inner logs and investigate further.
koraybalci
#2 Posted : Monday, February 21, 2022 5:51:34 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/6/2019(UTC)
Posts: 5
Location: Australia

Thanks: 3 times
Sometimes, after a very long while, NCrunch stops processing but can't find any test. Message I see at the top is: "No tests are queued for execution. Monitoring no tests, with no tests ignored." In that solution, there are tests of course. Both NUnit and XUnit.
Remco
#3 Posted : Monday, February 21, 2022 8:26:22 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,571

Thanks: 862 times
Was thanked: 1176 time(s) in 1097 post(s)
Hi, thanks for sharing this issue.

I've successfully reproduced this problem under the new preview build of VS2022 (17.2.0 preview 1).

The issue appears intermittently, so sometimes it works and sometimes it doesn't. The cause appears to be a change made to the threading model in the VS project system. Essentially, the project system throws a locking exception when critical elements of projects in the system are read, claiming that a read lock is not enough. This looks like a preview bug to me, so I would prefer to avoid implementing messy workarounds in NCrunch before knowing whether MS continue to maintain this behaviour outside of a preview build.

So in short, we can't support this build of VS right now and will monitor the problem. For the time being, please roll back to a non preview build of VS.
2 users thanked Remco for this useful post.
koraybalci on 2/21/2022(UTC), b33rdy on 2/23/2022(UTC)
NeilMacMullen
#4 Posted : Monday, February 21, 2022 12:11:10 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 12/15/2016(UTC)
Posts: 49
Location: United Kingdom

Thanks: 26 times
Was thanked: 11 time(s) in 10 post(s)
This is also what I saw in this thread... https://forum.ncrunch.ne...s-to-break-Ncrunch.aspx The behaviour has definitely "come and gone" across different preview versions. At the moment I've reverted to the non-preview of VS2022 which appears to work ok.
1 user thanked NeilMacMullen for this useful post.
koraybalci on 2/21/2022(UTC)
jschreuder
#5 Posted : Monday, February 28, 2022 1:14:10 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/5/2015(UTC)
Posts: 39
Location: Australia

Thanks: 11 times
Was thanked: 22 time(s) in 10 post(s)
I just submitted a bug report probably related to this too (VS 2022 17.2 Preview 1) before I saw this thread.
I'm going to downgrade and see if it's ok on latest RTM build

EDIT: Seems good on 17.1
koraybalci
#6 Posted : Tuesday, March 1, 2022 12:28:04 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/6/2019(UTC)
Posts: 5
Location: Australia

Thanks: 3 times
I moved away from preview and happy now. (I wasn't aware non-preview/real 2022 is already out there :) ).

Thanks a lot.
arkiaconsulting
#7 Posted : Friday, March 18, 2022 1:34:09 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/30/2019(UTC)
Posts: 7
Location: France

Thanks: 2 times
Was thanked: 10 time(s) in 5 post(s)
Now working in 17.2.0 Preview 2.0
2 users thanked arkiaconsulting for this useful post.
Remco on 3/18/2022(UTC), NeilMacMullen on 3/21/2022(UTC)
arkiaconsulting
#8 Posted : Tuesday, March 22, 2022 1:23:26 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/30/2019(UTC)
Posts: 7
Location: France

Thanks: 2 times
Was thanked: 10 time(s) in 5 post(s)
arkiaconsulting;16033 wrote:
Now working in 17.2.0 Preview 2.0


Actually, it's been working for one day only... :-(
arkiaconsulting
#9 Posted : Tuesday, March 22, 2022 1:33:13 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/30/2019(UTC)
Posts: 7
Location: France

Thanks: 2 times
Was thanked: 10 time(s) in 5 post(s)
Looks like there is a workaround:
- Close VS
- Remove the `.vs` hidden solution folder
- re-launch VS

And nCrunch is back (tested on 17.2.0 Preview 2.0)
2 users thanked arkiaconsulting for this useful post.
NeilMacMullen on 3/23/2022(UTC), jonas on 4/26/2022(UTC)
jonas
#10 Posted : Tuesday, April 26, 2022 7:10:34 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/6/2018(UTC)
Posts: 7
Location: Denmark

Thanks: 5 times
Was thanked: 1 time(s) in 1 post(s)
arkiaconsulting;16041 wrote:
Looks like there is a workaround:
- Close VS
- Remove the `.vs` hidden solution folder
- re-launch VS

And nCrunch is back (tested on 17.2.0 Preview 2.0)



Thank you! I just did this on 17.2.0 Preview 4 and it worked. Lifesaver!
arkiaconsulting
#11 Posted : Sunday, May 1, 2022 9:36:10 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/30/2019(UTC)
Posts: 7
Location: France

Thanks: 2 times
Was thanked: 10 time(s) in 5 post(s)
Even better workaround: you may disable the preview feature:
Quote:
Use the project cache to speed solution load
.

That way, the file
Quote:
***.metadata.v2
under the folder
Quote:
.vs/ProjectEvaluation
(which is actually the reason why nCrunch is unable to load) doesn't get created.
1 user thanked arkiaconsulting for this useful post.
NeilMacMullen on 5/5/2022(UTC)
NeilMacMullen
#12 Posted : Thursday, May 5, 2022 11:20:53 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 12/15/2016(UTC)
Posts: 49
Location: United Kingdom

Thanks: 26 times
Was thanked: 11 time(s) in 10 post(s)
>Even better workaround: you may disable the preview feature:

Thanks so much - tried this on preview 6 and it seems to do the trick.
UppSol
#13 Posted : Tuesday, May 10, 2022 7:55:49 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 3/21/2019(UTC)
Posts: 37
Location: Austria

Thanks: 29 times
Was thanked: 7 time(s) in 7 post(s)
@Remco

Now that 17.2 RTM(https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-2-is-now-available/) has been released, will NCrunch support the new/preview feature that caused trouble in the preview version?
I haven't got time to check if it works or not.

Br
Remco
#14 Posted : Tuesday, May 10, 2022 11:57:41 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,571

Thanks: 862 times
Was thanked: 1176 time(s) in 1097 post(s)
UppSol;16110 wrote:

Now that 17.2 RTM(https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-2-is-now-available/) has been released, will NCrunch support the new/preview feature that caused trouble in the preview version?
I haven't got time to check if it works or not.


Yes. I implemented a workaround for this problem yesterday, as it was looking like it would be in the RTM. I was also hoping for another week to add features, but it looks like v4.13 is now going to need to be released as soon as possible.
2 users thanked Remco for this useful post.
UppSol on 5/11/2022(UTC), MaxRonin on 5/11/2022(UTC)
MaxRonin
#15 Posted : Wednesday, May 11, 2022 10:36:38 AM(UTC)
Rank: Member

Groups: Registered
Joined: 3/18/2016(UTC)
Posts: 27
Location: Austria

Thanks: 9 times
Was thanked: 2 time(s) in 2 post(s)
Hmm, so I just got here because I innocently upgraded VS to 17.2 and now NCrunch is not working anymore.

I followed the advise to deactivate the "Use project cache..." feature *AND* deleted the *.metadata file in .vs/ProjectEvaluation, but it still doesn't work. And, interestingly, when I restart VS, while the feature still shows as deactivated, the metadata file is back.

Any idea what I can do short of downgrading VS?
MaxRonin
#16 Posted : Wednesday, May 11, 2022 10:44:05 AM(UTC)
Rank: Member

Groups: Registered
Joined: 3/18/2016(UTC)
Posts: 27
Location: Austria

Thanks: 9 times
Was thanked: 2 time(s) in 2 post(s)
Aha, in my case, I had to delete the while ProjectEvaluation folder, not just the metadata file, in addition to deactivating the feature.
Remco
#17 Posted : Wednesday, May 11, 2022 12:41:04 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,571

Thanks: 862 times
Was thanked: 1176 time(s) in 1097 post(s)
A workaround for this problem has been implemented in NCrunch v4.12, which is now available for download.
2 users thanked Remco for this useful post.
UppSol on 5/11/2022(UTC), MaxRonin on 5/12/2022(UTC)
UppSol
#18 Posted : Wednesday, May 11, 2022 5:40:14 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 3/21/2019(UTC)
Posts: 37
Location: Austria

Thanks: 29 times
Was thanked: 7 time(s) in 7 post(s)
Remco;16114 wrote:
A workaround for this problem has been implemented in NCrunch v4.12, which is now available for download.



Great support, as always!

Thank you very much 👍
1 user thanked UppSol for this useful post.
Remco on 5/11/2022(UTC)
Users browsing this topic
Guest
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.094 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download