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
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
The main purpose was to fix a Firefox CI test error on one of the util tests - a recent version of Firefox causes the error class to no longer be stored in error.stack and our test that checks for the "FirebaseError" string on a purposefully thrown error now fails. There's no recognizable string in the stack anymore (just code locations), so I just changed it to just check for its existence.
In the course of trying to diagnose this I followed a false trail thinking it might be because Node tests were running during Firefox and Webkit tests. That wasn't the cause but they shouldn't be running during those jobs, it's pointless. Node tests already run during the main Chrome test job. I changed it so that all packages running a cross-browser test use:
"test:browser" if available
special npm script like "test:browser:unit" if specified in the map of special packages (this functionality already existed), to avoid "test:browser:integration" and the like
fall back to "test" if none of those is available
This should make those jobs a little faster and more streamlined.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
A newer major version of the mock responses for Vertex AI unit tests is available. update_vertexai_responses.sh should be updated to clone the latest version of the responses: v13.0
This report is too large (255,672 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.
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.
The main purpose was to fix a Firefox CI test error on one of the util tests - a recent version of Firefox causes the error class to no longer be stored in
error.stack
and our test that checks for the "FirebaseError" string on a purposefully thrown error now fails. There's no recognizable string in the stack anymore (just code locations), so I just changed it to just check for its existence.In the course of trying to diagnose this I followed a false trail thinking it might be because Node tests were running during Firefox and Webkit tests. That wasn't the cause but they shouldn't be running during those jobs, it's pointless. Node tests already run during the main Chrome test job. I changed it so that all packages running a cross-browser test use:
This should make those jobs a little faster and more streamlined.