about summary refs log tree commit diff
path: root/pkgs/servers/home-assistant/tests.nix
AgeCommit message (Collapse)AuthorFilesLines
2024-06-07home-assistant: 2024.5.5 -> 2024.6.0Martin Weinelt1-0/+3
https://www.home-assistant.io/blog/2024/06/05/release-20246/
2024-05-10home-assistant: disable failing testMartin Weinelt1-3/+19
Update set of disabled tests in time for NixOS 24.05.
2024-03-07home-assistant: 2024.2.5 -> 2024.3.0Martin Weinelt1-0/+5
https://www.home-assistant.io/blog/2024/03/06/release-20243/
2024-01-05home-assistant: update disabled tests and dependenciesMartin Weinelt1-66/+41
2024-01-04home-assistant: mark telegram test brokenMartin Weinelt1-0/+2
2024-01-04home-assistant: 2023.12.4 -> 2024.1.0Martin Weinelt1-0/+4
https://www.home-assistant.io/blog/2024/01/03/release-20241/
2023-11-14home-assistant: update disabled testsMartin Weinelt1-0/+6
The test on sma has been failing since the 2023.10.0 release. The telegram_bot tests have had a failing dependency since we updated urllib3>=2.0 and it's too much of a hassle to override this dependency.
2023-10-05home-assistant: 2023.9.3 -> 2023.10.0Martin Weinelt1-0/+2
https://www.home-assistant.io/blog/2023/10/04/release-202310/
2023-09-08home-assistant: 2023.8.4 -> 2023.9.0Martin Weinelt1-0/+8
https://github.com/home-assistant/core/releases/tag/2023.9.0
2023-08-02home-assistant: 2023.7.3 -> 2023.8.0Martin Weinelt1-0/+10
https://www.home-assistant.io/blog/2023/08/02/release-20238/
2023-06-25home-assistant: 2023.6.2 -> 2023.6.3Martin Weinelt1-0/+12
https://github.com/home-assistant/core/releases/tag/2023.6.3
2023-06-08home-assistant-component-tests: disable xdistMartin Weinelt1-1/+0
We have enough components that we can parallelize them when tested in bulk, but even with one xdist thread some tests fail every once in a while.
2023-04-06home-assistant: 2023.3.6 -> 2023.4.0Martin Weinelt1-7/+6
https://www.home-assistant.io/blog/2023/04/05/release-20234/
2023-03-03Merge remote-tracking branch 'origin/staging-next' into stagingMartin Weinelt1-1/+6
2023-03-02home-assistant-component-tests: Reduce to two parallel test runnersMartin Weinelt1-1/+1
The component tests are rather short, and each runner has a certain setup cost. So we're better off, just starting fewer of them and have them do more work. It also works around a race condition, that upstream likely isn't running into, because of the hardware specs¹ for the runners. [1] https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources
2023-03-02home-assistant: 2023.2.5 -> 2023.3.0Martin Weinelt1-0/+5
https://www.home-assistant.io/blog/2023/03/01/release-20233/
2023-02-19python310Packages.pychromecast: Normalize attribute nameMartin Weinelt1-1/+1
2023-02-03home-assistant: Update dependencies and testsMartin Weinelt1-2/+2
2023-02-02home-assistant: 2023.1.7 -> 2023.2.0Martin Weinelt1-34/+3
https://www.home-assistant.io/blog/2023/02/01/release-20232/
2023-01-21treewide: switch to nativeCheckInputsGuillaume Girol1-1/+1
checkInputs used to be added to nativeBuildInputs. Now we have nativeCheckInputs to do that instead. Doing this treewide change allows to keep hashes identical to before the introduction of nativeCheckInputs.
2023-01-19home-assistant-component-tests.homeassistant_hardware: Mark brokenMartin Weinelt1-0/+3
All tests are currently being skipped so they result in an error.
2023-01-05home-assistant: 2022.12.9 -> 2023.1.0Martin Weinelt1-0/+1
https://www.home-assistant.io/blog/2023/01/04/release-20231/
2022-12-08home-assistant: 2022.11.5 -> 2022.12.0Martin Weinelt1-1/+7
https://www.home-assistant.io/blog/2022/12/07/release-202212/
2022-11-05home-assistant: 2022.10.5 -> 2022.11.1Martin Weinelt1-2/+8
https://www.home-assistant.io/blog/2022/11/02/release-202211/ https://github.com/home-assistant/core/releases/tag/2022.11.1
2022-10-06home-assistant: 2022.9.7 -> 2022.10.0Martin Weinelt1-0/+2
"All over the place" https://www.home-assistant.io/blog/2022/10/05/release-202210/
2022-09-30home-assistant: 2022.9.1 -> 2022.9.7Martin Weinelt1-3/+9
https://github.com/home-assistant/core/releases/tag/2022.9.7 https://github.com/home-assistant/core/releases/tag/2022.9.6 https://github.com/home-assistant/core/releases/tag/2022.9.5 https://github.com/home-assistant/core/releases/tag/2022.9.4 https://github.com/home-assistant/core/releases/tag/2022.9.3 https://github.com/home-assistant/core/releases/tag/2022.9.2
2022-09-19home-assistant-component-tests: build with format otherMartin Weinelt1-0/+1
2022-09-10home-assistant: 2022.8.7 -> 2022.9.0Martin Weinelt1-0/+3
https://www.home-assistant.io/blog/2022/09/07/release-20229/
2022-08-16home-assistant: 2022.8.4 -> 2022.8.5Martin Weinelt1-0/+1
https://github.com/home-assistant/core/releases/tag/2022.8.5
2022-07-07home-assistant: 2022.6.7 -> 2022.7.0Martin Weinelt1-3/+21
https://www.home-assistant.io/blog/2022/07/06/release-20227/
2022-06-01python3Packages.dsmr-parser: 0.32 -> 0.33Martin Weinelt1-0/+1
2022-05-22python3Packages.airtouch4pyapi: make compatible with Home AssistantRobert Schütz1-1/+0
2022-04-17Merge remote-tracking branch 'origin/master' into staging-nextMartin Weinelt1-0/+1
2022-04-17home-assistant: update component-packagesRobert Schütz1-0/+1
2022-04-15home-assistant: reduce component tests processesMartin Weinelt1-0/+4
Component tests are often of lesser quality, which may lead to spurious errors when run with high parallelization. Reducing to 4 processes aligns the setup with what GitHub actions provides, which is what upstream uses to test.
2022-04-07home-assistant: 2022.3.8 -> 2022.4.0Martin Weinelt1-5/+8
https://www.home-assistant.io/blog/2022/04/06/release-20224/
2022-03-04home-assistant: 2022.2.9 -> 2022.3.0Martin Weinelt1-1/+11
2022-02-09home-assistant: add aioaseko as implicit version test dependencyMartin Weinelt1-0/+1
2022-02-03home-assistant: 2021.12.10 -> 2022.2.0Martin Weinelt1-5/+2
https://www.home-assistant.io/blog/2022/02/02/release-20222/
2022-01-16home-assistant: outsource component testsRobert Schütz1-0/+69
A component's tests can now be run by building home-assistant.tests.components.${component} Co-authored-by: Martin Weinelt <hexa@darmstadt.ccc.de>