Skip to content

Test Host Process Crashes After 5.0.1 Upgrade #535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adamrodger opened this issue Mar 28, 2025 · 1 comment
Open

Test Host Process Crashes After 5.0.1 Upgrade #535

adamrodger opened this issue Mar 28, 2025 · 1 comment
Labels
bug Indicates an unexpected problem or unintended behavior triage This issue is yet to be triaged by a maintainer

Comments

@adamrodger
Copy link
Contributor

Version information:

  • OS: Linux x64
  • PactNet Version: 5.0.1
  • .Net Version: 9.0

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:

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.

@adamrodger 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
@adamrodger
Copy link
Contributor Author

adamrodger commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior triage This issue is yet to be triaged by a maintainer
Projects
None yet
Development

No branches or pull requests

1 participant