8000 Flaky tests · Issue #10966 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Closed
6 of 15 tasks
MartinHjelmare opened this issue Dec 5, 2017 · 17 comments · Fixed by #17376
Closed
6 of 15 tasks

Flaky tests #10966

MartinHjelmare opened this issue Dec 5, 2017 · 17 comments · Fixed by #17376
Labels

Comments

@ChristianKuehnel
Copy link
Contributor
8000 ChristianKuehnel commented Jan 6, 2018

I have one more: TestCanarySensorSetup.test_setup_sensors

@MartinHjelmare
Copy link
Member Author

The vultr test should be fixed by:
#11477

@MartinHjelmare
Copy link
Member Author

CC @snjoetw about the canary test that is flaky.

@MartinHjelmare
Copy link
Member Author

Canary test should be fixed by:
#11519

@ReneNulschDE
Copy link
Contributor

I have one more: tests.components.weather.test_darksky.TestDarkSky

@ChristianKuehnel
Copy link
Contributor

@balloobbot
Copy link

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 👍

@MartinHjelmare
Copy link
Member Author

All of these are not fixed yet I think.

@MartinHjelmare
Copy link
Member Author

@mxworm looks like homematicip cloud is doing I/O in the first config flow test. It's not patched in the correct place:
https://travis-ci.org/home-assistant/home-assistant/jobs/440417606#L1102

@balloob
Copy link
Member
balloob commented Nov 30, 2018

Not sure how we should organize this issue as the maxage one is currently very prevalent. Geofency just got fixed :)

@MartinHjelmare
Copy link
Member Author

How do you mean? That we shouldn't have an open issue to track known flaky tests?

@balloob
Copy link
Member
balloob commented Dec 2, 2018

Not sure. Maybe I'll just update the list to show which tests are still flaky and which ones are no longer an issue.

@balloobbot
Copy link

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 👍

@MartinHjelmare
Copy link
Member Author

There are still flaky tests.

@cgtobi
Copy link
Contributor
cgtobi commented Apr 15, 2019

Another flaky test #23092

@stale
Copy link
stale bot commented Jul 14, 2019

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 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 14, 2019
@MartinHjelmare
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
0