I'm having issue with our Pactflow comparisons sud...
# pactflowb
Becky Fulton
12/21/2023, 4:00 PMI'm having issue with our Pactflow comparisons suddenly being incredibly slow. I'm currently at 16 mins and counting for the latest one. Anyone else having this issue? Any suggestions of how to resolve it?
m
Matt (pactflow.io / pact-js / pact-go)
12/21/2023, 10:06 PM
When you say comparisons, are you referring to BDCT or provider verification?
b
Becky Fulton
12/22/2023, 9:22 AMSorry I'm not really sure what either of those terms refers to. It's the Pact broker can-i-deploy check that compares the consumer and provider specs to see if they're compatible. We've had a lot of failures of this because it says the cross contract comparison is still being executed.
m
Matt (pactflow.io / pact-js / pact-go)
12/22/2023, 10:04 AM
Ok then you are using bi directional contract testing (or BDCT for short, sorry)
đź‘Ť 1
Matt (pactflow.io / pact-js / pact-go)
12/22/2023, 10:11 AM
It can be due to a few things. The complexity of the comparison (although usually each comparison is sub minute). If you have a lot of branches that can also contribute. One option is to delete old branches (e.g. after merging)
Matt (pactflow.io / pact-js / pact-go)
12/22/2023, 10:14 AM
b
Becky Fulton
12/22/2023, 10:17 AMThanks, will give it go!
Becky Fulton
12/22/2023, 10:23 AMHi @Matt (pactflow.io / pact-js / pact-go) when I try the request from that API I get this error
You need to send the SwaggerHub Portal cookie with this requestBecky Fulton
12/22/2023, 10:30 AMOh weirdly it's started working now 🤷‍♀️
m
Matt (pactflow.io / pact-js / pact-go)
01/08/2024, 2:07 AM
After investigation, some of the comparisons are queueing up much longer than anticipated. We will be pushing out a change in the next iteration to
1. Increase the number of workers processing the comparisons
2. Reducing the number of (recent) branches we “pre-calculate” results for
This just means any branches not in the pre-calculated list will be determined on-demand in the
can-i-deploy