Temporarily disable two flaky InAppPurchaseStoreTests test cases
#8599
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…at call `userIsEntitledToProduct`.
Collaborator
You can test the changes from this Pull Request by:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Temporarily for #8221
Description
We've tried a few ways to fix two flaky tests that call
InAppPurchaseAction.userIsEntitledToProduct, but haven't found a fix yet that can pass consistently when running the same test cases several times #8256 (review). Let's disable them for now and come up with a way to make them pass consistently, possibly when we're going to launch IAP. This helps us unblock PR merging and save CI resources.Testing instructions
Just CI.
RELEASE-NOTES.txtif necessary.