-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Flaky tests #10966
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
Comments
I have one more: TestCanarySensorSetup.test_setup_sensors |
The vultr test should be fixed by: |
CC @snjoetw about the canary test that is flaky. |
Canary test should be fixed by: |
I have one more: tests.components.weather.test_darksky.TestDarkSky |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
All of these are not fixed yet I think. |
@mxworm looks like homematicip cloud is doing I/O in the first config flow test. It's not patched in the correct place: |
Not sure how we should organize this issue as the maxage one is currently very prevalent. Geofency just got fixed :) |
How do you mean? That we shouldn't have an open issue to track known flaky tests? |
Not sure. Maybe I'll just update the list to show which tests are still flaky and which ones are no longer an issue. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
There are still flaky tests. |
Another flaky test #23092 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I think there are no running tests at the moment that are flaky. We have either fixed them or disabled them. We could close this for now. |
Uh oh!
There was an error while loading. Please reload this page.
Issue to track known flaky tests. Let's fix them!
Currently impacting a lot of CI runs:
Others:
The text was updated successfully, but these errors were encountered: