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
Provider tests result in failed verification for Pending Pacts - Unexpected end event for Pact #1221
Comments
Looks like this is the line that is raising the exception: https://github.com/gradle/gradle/blob/master/subprojects/testing-jvm/src/main/java/org/gradle/api/internal/tasks/testing/junit/JUnitTestEventAdapter.java#L123 From what I can tell from that class, the test description is changing from when the test is started and when it is finished. The test descriptions are cached based on a key calculated from the interaction, so I wonder if you have another test which has the same key and is updating the description while that test is running. The key is calculated based on the provider states and the description. |
Well, we ended up deleting all the existing pacts, and everything works now. We think it was put into a bad state when playing with things locally. We didn't have anything meaningful, since it had not even been deployed anywhere since we added pacts. Likely, put into a bad state when teaching others or something. |
I have the same issue, pacts have no state but have descriptions. I have about twenty pacticipants in the Broker and look like it's relevant for most of them... deletion is not a good workaround for me, @uglyog what can you advice? Verification is okay, but it
|
@artemptushkin can you check that the descriptions are unique? |
@uglyog descriptions are not unique, this is relevant for a lot of different integrations. Probably appeared after PactBroker update from |
Our verification results are failing to publish when pending pacts are enabled. If we disable pending pacts, everything works fine.
Using Gradle 6.5
testCompile group: 'au.com.dius.pact.provider', name: 'spring', version: '4.1.6'
Redacted debug logs
The VerificationResult is OK until it's passed to the test notifier
This is the stacktrace from the thrown exception
The text was updated successfully, but these errors were encountered: