-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: Stop suppressing pod install failures #12485
Merged
Merged
+2
−2
Conversation
This file contains 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
Gudahtt
force-pushed
the
stop-suppressing-pod-install-failures
branch
from
November 28, 2024 21:38
205def9
to
eecd3d3
Compare
Gudahtt
added
No E2E Smoke Needed
If the PR does not need E2E smoke test run
No QA Needed
Apply this label when your PR does not need any QA effort.
labels
Nov 28, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12485 +/- ##
==========================================
+ Coverage 56.41% 57.04% +0.63%
==========================================
Files 1797 1817 +20
Lines 40586 40875 +289
Branches 5097 5166 +69
==========================================
+ Hits 22896 23318 +422
+ Misses 16134 15974 -160
- Partials 1556 1583 +27 ☔ View full report in Codecov by Sentry. |
Gudahtt
force-pushed
the
stop-suppressing-pod-install-failures
branch
from
December 5, 2024 23:46
c2be77a
to
f5589dd
Compare
Depends upon #12574 |
Gudahtt
commented
Dec 5, 2024
tommasini
approved these changes
Dec 6, 2024
Pod install failures were suppressed originally to make cross-platform development easier, as they would fail on Windows and Linux (where you would presumably be developing with Android which does not require this step). However, since the introduction of the new setup script, this step will not run on non-macOS machines by default so this error suppression is no longer needed. This will make install errors easier to discover, saving developer time.
Gudahtt
force-pushed
the
stop-suppressing-pod-install-failures
branch
from
December 6, 2024 19:00
f5589dd
to
be8f618
Compare
Quality Gate passedIssues Measures |
metamaskbot
added
the
release-7.38.0
Issue or pull request that will be included in release 7.38.0
label
Dec 6, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
No E2E Smoke Needed
If the PR does not need E2E smoke test run
No QA Needed
Apply this label when your PR does not need any QA effort.
release-7.38.0
Issue or pull request that will be included in release 7.38.0
team-mobile-platform
team-wallet-framework
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.
Description
Pod install failures were suppressed originally to make cross-platform development easier, as they would fail on Windows and Linux (where you would presumably be developing with Android which does not require this step). However, since the introduction of the new setup script, this step will not run on non-macOS machines by default so this error suppression is no longer needed.
This will make install errors easier to discover, saving developer time.
Related issues
N/A
Manual testing steps
To test that there is no regression, simply run
yarn setup
.I'm not entirely sure how to induce a pod install error. But if you're in a state where pod install fails, then
yarn setup
should now fail as well, where previously it would succeed.I simulated a failure by updating
pod:install
to saybundle exec po install
(i.e. delete thed
frompod
so that it's an unrecognized command). This failure showed on the CLI as expected on this branch. Onmain
it silently failed.Screenshots/Recordings
N/A
Pre-merge author checklist
Pre-merge reviewer checklist