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

Notification

Icon
Error

Issue running tests which use embedded event store
samholder
#1 Posted : Monday, June 12, 2017 1:39:48 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)
Hi,

We are trying to get our integration tests to use event store's embedded option, but these tests fail saying this as part of the message when we try and get the status of a projection we have just created:

"status": "Faulted",
"stateReason": "The projection subsystem failed to load a libjs1.so/js1.dll/... or one of its dependencies. The original error message is: Unable to load DLL 'js1': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"


I'm not sure what the exact issue is here, but I expect its something to do with how NCrunch is resolving the dependencies when the tests run, and how event store is distributing the dlls in its embeeded nuget package.

I have created a minimal project which replicates this issue in the hope that this will enable you to recreate the issue. The zip file containing the project can be found here: (- BROKEN LINK -)

let me know if this is not enough information to be going on, or if I can help in any other way. I'll also cross post into the event store google group in case they have any ideas.

Thanks

Sam
Remco
#2 Posted : Monday, June 12, 2017 11:09:49 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for sharing this problem and for the sample solution.

Unfortunately, I couldn't get the sample to run. It seems to fail with connectivity related issues before it reaches the assembly resolution problem.

On inspection of the Nuget packages, I couldn't find any binaries or resources named according to the error you've shown above. It makes me wonder if the file may be distributed separately or is perhaps dynamically generated. Usually the 'Copy referenced assemblies to workspace' setting can resolve most of these sorts of issues, as NCrunch then copies the dependencies into the build output directory as per the normal build system. I don't have any firsthand experience with this library so unfortunately I'm not sure if it has some kind of specialised search logic that looks elsewhere. Sorry, I wish I could be of more help.
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.026 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download