| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
✅ Integration test succeeded!Requested by @dconeybe on commit a31c796 |
Sorry, something went wrong.
|
Looks like there are some failures, at least on Windows |
Sorry, something went wrong.
I'm not sure what was going on there. I've merged in main to see if that fixes anything. The desktop.yml that was used was not consistent with HEAD of the main branch. |
Sorry, something went wrong.
|
@jonsimantov It looks like ctest is trying to run the grpc tests, and those tests don't get compiled. This is odd because when I build everything via cmake locally, ctest does not try to run the grpc tests. Any ideas why it's trying to run the grpc tests and failing to build them? |
Sorry, something went wrong.
|
Hmm, I'm not sure why that would be any different here than in previous occasions. @a-maurice any ideas? |
Sorry, something went wrong.
|
@jonsimantov @a-maurice Many of the same build errors occur when pointing the C++ SDK at the HEAD of the master branch of the firebase-ios-sdk repository: #950. I'm going to move my investigation to that PR until it goes green. |
Sorry, something went wrong.
|
I'm guessing that the upgrade of grpc in the iOS SDK is the culprit: firebase/firebase-ios-sdk#9488. I think we just need to set the cmake cache variable to disable the "re2" tests (RE2_BUILD_TESTING). |
Sorry, something went wrong.
… PR that adds Snappy support has been merged there
…tic python_setup.cmake bug
…, which fixes a problematic usage of designated initialization
|
@jonsimantov Can you take a look at this PR? I won't merge it into main but rather into the PR that updates the iOS dependencies. |
Sorry, something went wrong.
| URL https://github.com/firebase/firebase-ios-sdk/archive/${version}.tar.gz | ||
| GIT_REPOSITORY "https://github.com/firebase/firebase-ios-sdk.git" | ||
| # Pinned HEAD commit as of June 01, 2022 @ 10:51 EDT. | ||
| GIT_TAG 89c38d1ed908dbc10d5f9f7aded4cf271113773f |
There was a problem hiding this comment.
Shouldn't GIT_TAG be ${version}, which will be updated to 9.2.0 or whatever when the time comes?
Sorry, something went wrong.
There was a problem hiding this comment.
Ahh yes, this particular part of the PR will be reverted. It's just here so I can test again the HEAD of the firebase-ios-sdk.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, but as noted in the PR, we'll keep this a draft and merge it into the upcoming iOS dependency update.
Sorry, something went wrong.
### iOS - Firebase/Analytics → 9.2.0 - Firebase/Auth → 9.2.0 - Firebase/Core → 9.2.0 - Firebase/Crashlytics → 9.2.0 - Firebase/Database → 9.2.0 - Firebase/DynamicLinks → 9.2.0 - Firebase/Firestore → 9.2.0 - Firebase/Functions → 9.2.0 - Firebase/Installations → 9.2.0 - Firebase/Messaging → 9.2.0 - Firebase/RemoteConfig → 9.2.0 - Firebase/Storage → 9.2.0 > Created by [Update Android and iOS dependencies workflow](https://github.com/firebase/firebase-cpp-sdk/actions/runs/2544841237).
…220622-200757' into SnappyPatchRevert
|
The changes in this PR were merged into the main branch in #1003 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Remove the logic to patch the firebase-ios-sdk dependency to add Snappy support.
This PR will need to be merged when this SDK updates its dependency on the firebase-ios-sdk repository since firebase/firebase-ios-sdk#9596 has been merged to add Snappy support directly in the iOS SDK.
The Snappy patching was originally added by #885. This PR effectively reverts that PR now that Snappy support is natively added to the firebase-ios-sdk repository.
Googlers see b/227782613 for more details.