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
{{ message }}
Repository navigation
Linux firebase_release_smoke_test timing out #144183
#144234 moves firebase_abstract_method_smoke_test and firebase_android_embedding_v2_smoke_test to staging, considering the issue is still not resolved.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-]Linux firebase_release_smoke_test[/-][+]Linux firebase_release_smoke_test timing out[/+]keyonghan commentedon Feb 26, 2024
Reaching out to firebase team.
keyonghan commentedon Feb 26, 2024
FTL is experiencing networking issue: http://omg/70161
We can mark the target as
bringup: trueto unblock. /cc @PiinksPiinks commentedon Feb 26, 2024
Thanks @keyonghan!
Mark firebase_release_smoke_test as `bringup: true` (#144186)
keyonghan commentedon Feb 27, 2024
#144234 moves
firebase_abstract_method_smoke_testandfirebase_android_embedding_v2_smoke_testto staging, considering the issue is still not resolved.Mark two other firebase targets as bringup: true (#144234)
keyonghan commentedon Feb 28, 2024
Issue seems mitigated, but I still see a failed build today. Need monitor a bit more.

keyonghan commentedon Feb 29, 2024
The issue has been mitigated, but the omg is still open. Will monitor a bit more before closing (moving targets back to prod).
keyonghan commentedon Mar 6, 2024
Tests have been passing consistently for days. Though the omg is still open, proactively bringing these back to prod. #144703
Bring back firebase tests to prod (#144703)
keyonghan commentedon Mar 7, 2024
Targets have been moved to prod. Closing.
github-actions commentedon Mar 21, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.