8000 Failing builds because of recorder/sqlalchemy · Issue #11252 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Failing builds because of recorder/sqlalchemy #11252

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
ChristianKuehnel opened this issue Dec 20, 2017 · 1 comment
Closed

Failing builds because of recorder/sqlalchemy #11252

ChristianKuehnel opened this issue Dec 20, 2017 · 1 comment

Comments

@ChristianKuehnel
Copy link
Contributor
ChristianKuehnel commented Dec 20, 2017

Home Assistant release (hass --version):
dev and master branches

Python release (python3 --version):
all

Component/platform:
recorder

Description of problem:
Today I've run several builds on TravisCI and I've seen several test failures related to the recorder. Where none of the changes was in any way related to the recorder. Since it's a sporadic issue I guess this is some sort of race condition/concurrency issue...

Some examples I could still dig up:

Here's an example log file in case the build logs disappear:
https://gist.github.com/ChristianKuehnel/acdd424dde001654b16b8a890b0a7136

Expected:
Tests should be deterministic, if there's something broken, the test should always fail.

Problem-relevant configuration.yaml entries and steps to reproduce:
The problem is non-deterministic. So I don't really know what triggers it.

@MartinHjelmare
Copy link
Member

Duplicate of #10966.

@home-assistant home-assistant locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0