search

microsoft / azuredevopslabs

Learn how you can plan smartly, collaborate better, and ship faster with a set of modern development services with Azure DevOps.
https://www.azuredevopslabs.com
MIT License
832 stars 928 forks source link

Parts Unlimited-ASP.NET-CI pipeline failed #605

Open rcaball opened 2 years ago

rcaball commented 2 years ago

Hi all,

I've created Parts Unlimited-ASP.NET-CI pipeline following lab instruction, however after running I see the following errors:

Error: The process 'D:\a_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.195.0\Modules\DTAExecutionHost.exe' failed with exit code 1

[warning]Vstest failed with error. Check logs for failures. There might be failed tests.

[error]Error: The process 'D:\a_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.195.0\Modules\DTAExecutionHost.exe' failed with exit code 1

[error]Vstest failed with error. Check logs for failures. There might be failed tests.

Thanks in advance, Raquel

juanandmsft commented 2 years ago

Same problem here. Seems a problem with Castle.Core.dll version.

Error Message: Test method PartsUnlimited.UnitTests.Controllers.OrdersControllerTests.Order_DetailWithOrderDetails threw exception: System.TypeInitializationException: The type initializer for 'Moq.Mock`1' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Moq.Proxy.CastleProxyFactory' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'Castle.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

packages.config points to 4.0.0, not to 3.3.0.0

app.config and PartsUnlimited.UnitTests.csproj refer also to 4.0, but publicKeyToken matches the one in error for 3.0 app.config:

PartsUnlimited.UnitTests.csproj

Thanks.
juanandmsft commented 2 years ago

Build works from commit 816d9487 up to 5f9404c8 in master branch, all using vs2017-win2016 agent (windows-2019 fails). From that point, build fails. image

gayatriramac commented 2 years ago

Facing the same issue. @juanandmsft.. unable to find a solution..

juanandmsft commented 2 years ago

Three options here. Quickest one is run the pipeline specifying what commit to use for build. image Second option is overwriting latest code with one in commit 5f9404c8. And third option will be fixing code in master branch based on commit 5f9404c8.

Hope it helps.