| 5 Feb 2025 |
 @hexa:lossy.network | Very backup component heavy release | 19:30:39 |
 dotlambda | In reply to @hexa:lossy.network
api breakage I missed in the last aioesphomeapi update Weirdly https://github.com/home-assistant/core/commit/48a91540 didn't change any actual code | 19:48:06 |
| @hexa:lossy.network | hrm | 19:48:44 |
| @hexa:lossy.network | so where is the caller? | 19:49:01 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/379685 | 19:50:46 |
| @hexa:lossy.network | > Executing pytestCheckPhase
> ImportError while loading conftest '/build/source/tests/conftest.py'.
> tests/conftest.py:1240: in <module>
> @pytest_asyncio.fixture(autouse=True, scope="session", loop_scope="session")
> /nix/store/nvqmkrjzzbrzyhgym70530w06vmqad85-python3.13-pytest-asyncio-0.23.8/lib/python3.13/site-packages/pytest_asyncio/plugin.py:151: in inner
> return fixture(fixture_function, **kwargs)
> /nix/store/nvqmkrjzzbrzyhgym70530w06vmqad85-python3.13-pytest-asyncio-0.23.8/lib/python3.13/site-packages/pytest_asyncio/plugin.py:145: in fixture
> return pytest.fixture(fixture_function, **kwargs)
> E TypeError: fixture() got an unexpected keyword argument 'loop_scope'
For full logs, run 'nix log /nix/store/g9p6k7j61axy1ck6i2ph0zp69z4baxx4-homeassistant-2025.2.0.drv'.
| 19:54:55 |
| @hexa:lossy.network | fml | 19:54:57 |
| @hexa:lossy.network | depends on pytest-asyncio>=0.25.0 | 19:56:58 |
| @hexa:lossy.network | currently on staging-next | 19:57:02 |
| @hexa:lossy.network | rebasing onto staging-next | 20:01:18 |
| dotlambda | In reply to @hexa:lossy.network
rebasing onto staging-next That's probably a good idea anyway cause some of those updates might conflict with changes made in python-updates | 20:06:13 |
| @hexa:lossy.network | yep\ | 20:09:56 |
| @hexa:lossy.network | not sure the staging people are going to like me for it 😄 | 20:10:08 |
| @hexa:lossy.network | dotlambda: hm, there is something off with the component tests | 21:43:18 |
| @hexa:lossy.network | some of them run into this backtrace | 21:43:32 |
| @hexa:lossy.network | homeassistant-test-hassio> File "/build/source/homeassistant/components/hassio/coordinator.py", line 530, in _update_addon_info
homeassistant-test-hassio> info_dict = info.to_dict()
homeassistant-test-hassio> File "/nix/store/4nj4l3scr96gcx4jirb3kfv24c4ay1z7-python3-3.13.1/lib/python3.13/unittest/mock.py", line 1167, in __call__
homeassistant-test-hassio> return self._mock_call(*args, **kwargs)
homeassistant-test-hassio> File "/nix/store/4nj4l3scr96gcx4jirb3kfv24c4ay1z7-python3-3.13.1/lib/python3.13/unittest/mock.py", line 1171, in _mock_call
homeassistant-test-hassio> return self._execute_mock_call(*args, **kwargs)
homeassistant-test-hassio> RuntimeWarning: Enable tracemalloc to get the object allocation traceback
| 21:43:35 |
| dotlambda | In reply to @hexa:lossy.network
some of them run into this backtrace E.g. which component? | 23:48:31 |
| @hexa:lossy.network | e.g. hassio 😛 | 23:48:43 |
| @hexa:lossy.network | or nmbs | 23:49:17 |
| 6 Feb 2025 |
| dotlambda | In reply to @hexa:lossy.network
e.g. hassio 😛 fixture 'setup_integration' not found makes sense cause there is no such fixture in the hassio tests. It must be getting it from a different component but we run them in isolation | 00:06:24 |
| @hexa:lossy.network | huh, ok | 00:06:42 |
| dotlambda | It should have been setup_backup_integration instead | 00:19:03 |
| dotlambda | Anything else? | 00:19:08 |
| @hexa:lossy.network | posting a nixpkgs-review any minute now | 00:19:36 |
| @hexa:lossy.network | qtwebengine was taking its sweet time | 00:19:45 |
| @hexa:lossy.network | everything has been built and yet I'm still waiting for it to complete | 00:41:21 |
| dotlambda | I'm scared: https://github.com/home-assistant/core/pull/137495 ;-) | 00:43:45 |
| @hexa:lossy.network | it is there 😄 | 00:45:28 |
| @hexa:lossy.network | i wish you all the best | 00:46:06 |
| dotlambda | That llama stuff is so annoying. It always pollutes nixpkgs-review reports. | 00:50:48 |
