You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the upgrade from PactNet 5.0.0 to 5.0.1, I get an error when running provider tests inside a .Net Docker container:
The active test run was aborted. Reason: Test host process crashed
Test Run Aborted.
_VSTestConsole:
MSB4181: The "VSTestTask" task returned false but did not log an error.
1>Done Building Project "/app/tests/MyProject.Pacts/MyProject.Pacts.csproj" (VSTest target(s)) -- FAILED.
Build FAILED.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:03.52
Process exited with code 1
Test ignored: MyProject.ProviderTests.VerifyPacts, ignore reason: Interrupted by build execution timeout
Consumer tests work absolutely fine, it's only provider tests that crash.
Steps To Reproduce
Unsure currently - it was working fine before the upgrade
Additional context
The diff between 5.0.0 and 5.0.1 only really has an FFI upgrade in it, so I'm assuming the issue is there and that it's crashing the provider tests.
The text was updated successfully, but these errors were encountered:
adamrodger
added
bug
Indicates an unexpected problem or unintended behavior
triage
This issue is yet to be triaged by a maintainer
labels
Mar 28, 2025
I downgraded to 5.0.0 and the issue goes away. I'll try to see if there's a way to slowly increment the FFI version to work out which one breaks between 0.4.23 (v5.0.0) and 0.4.27 (v5.0.1), then maybe we can spot what causes this. I suspect the FFI either deadlocks, segfaults or panics, and that kills the .Net test process.
Version information:
Describe the bug
After the upgrade from PactNet 5.0.0 to 5.0.1, I get an error when running provider tests inside a .Net Docker container:
Consumer tests work absolutely fine, it's only provider tests that crash.
Steps To Reproduce
Unsure currently - it was working fine before the upgrade
Additional context
The diff between 5.0.0 and 5.0.1 only really has an FFI upgrade in it, so I'm assuming the issue is there and that it's crashing the provider tests.
The text was updated successfully, but these errors were encountered: