Encountering a strange issue, I've implemented some custom protocols recently and tests were passing fine locally using mix test.
The test that's failing inexplicably essentially grabs the metadata types my protocol is implemented for:
{_, impl_for} = MyProtocol.__protocol__(:impls).
This returns a list of metadata types just fine, but when I run mix test --cover, suddenly the test fails and I get:
** (MatchError) no match of right hand side value: :not_consolidated
I've tried consolidating the protocol manually in my test and I get {:error, :no_beam_info}
I'm encountering this discrepancy both locally and in our GH actions. Nothing seems to be of interest in our fairly minimal coveralls config, and our test config is setup to consolidate protocols as well.
Has anybody encountered this? I don't see any issues related to it and I've looked at everything on Google for protocol consolidation in regards to tests and excoveralls.
Encountering a strange issue, I've implemented some custom protocols recently and tests were passing fine locally using
mix test
.The test that's failing inexplicably essentially grabs the metadata types my protocol is implemented for:
{_, impl_for} = MyProtocol.__protocol__(:impls)
.This returns a list of metadata types just fine, but when I run
mix test --cover
, suddenly the test fails and I get:** (MatchError) no match of right hand side value: :not_consolidated
I've tried consolidating the protocol manually in my test and I get
{:error, :no_beam_info}
I'm encountering this discrepancy both locally and in our GH actions. Nothing seems to be of interest in our fairly minimal coveralls config, and our test config is setup to consolidate protocols as well.
Has anybody encountered this? I don't see any issues related to it and I've looked at everything on Google for protocol consolidation in regards to tests and excoveralls.