Test Lab Incident #20001
Firebase Test Lab experienced issues with tests.
Incident began at 2020-04-02 17:31 and ended at 2020-04-02 22:13 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Apr 02, 2020 | 22:13 | The issue with Firebase Test Lab has been resolved for all affected users as of Thursday, 2020-04-02 22:05 US/Pacific. |
|
| Apr 02, 2020 | 21:50 | Description: We believe the issue with Firebase Test Lab is mitigated for the most of the users. Less than 0.1% of tests on physical devices are possibly impacted. Virtual devices are unaffected. The rollback is till in progress with the ETA for full resolution in approximately two hours. We will provide an update by Friday, 2020-04-03 00:00 US/Pacific with current details. Diagnosis: Affected users can see infrastructure errors and increased pending time before tests become running. Workaround: None at this time. |
|
| Apr 02, 2020 | 19:53 | Description: We believe the issue with Firebase Test Lab is mitigated for the most of the users. Less than 0.5% of tests on physical devices are possibly impacted. Virtual devices are unaffected. We performing rollback with the ETA for full resolution in a few hours. We will provide an update by Thursday, 2020-04-02 22:00 US/Pacific with current details. Diagnosis: Affected users can see infrastructure errors and increased pending time before tests become running. Workaround: None at this time. |
|
| Apr 02, 2020 | 19:08 | Description: We believe the issue with Firebase Test Lab is mitigated for the most of the users. We do not have an ETA for full resolution at this point. We will provide an update by Thursday, 2020-04-02 21:00 US/Pacific with current details. Diagnosis: Affected users can see infrastructure errors and increased pending time before tests become running. Workaround: None at this time. |
|
| Apr 02, 2020 | 18:04 | Description: We are experiencing an intermittent issue with Firebase Test Lab, beginning at Thursday, 2020-04-02 17:00 US/Pacific. Symptoms: increased pending time, and infrastructure errors. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2020-04-02 20:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Affected users can see infrastructure errors and increased pending time before tests become running. Workaround: None at this time. |