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
Since there is only one configuration, I would expect the breakpoints A and B to be triggered exactly once. In my testing both A and B are triggered twice.
One more thing. The order does not seem to be consistent between runs (even multiple runs on the same build). Sometimes it is A,B,A,B and sometimes B,A,B,A. While this library does not promise a consistent order, this does seem strange and might indicate of a hidden bug.
The text was updated successfully, but these errors were encountered:
Hi zenled,
Thank you for reaching out and bringing this to our attention. Apologies for the delay in responding. Our team will review this issue promptly.
We appreciate your patience and understanding. If you have any additional details that could help, please feel free to share them here.
Best regards,
Filip
As explained here (1. Requirement check closure is called multiple times), the requirements check closure should be called only one time for each configuration.
Example:
Since there is only one configuration, I would expect the breakpoints
A
andB
to be triggered exactly once. In my testing bothA
andB
are triggered twice.One more thing. The order does not seem to be consistent between runs (even multiple runs on the same build). Sometimes it is
A,B,A,B
and sometimesB,A,B,A
. While this library does not promise a consistent order, this does seem strange and might indicate of a hidden bug.The text was updated successfully, but these errors were encountered: