Skip to content

Add versions to matrix and fix area test #1745

Add versions to matrix and fix area test

Add versions to matrix and fix area test #1745

Triggered via pull request April 6, 2024 11:10
Status Failure
Total duration 5m 41s
Artifacts

pytest.yaml

on: pull_request
Matrix: Run pytest
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 57 warnings, and 114 notices
Run pytest (3.11, 2023.8.4)
Process completed with exit code 1.
Run pytest (3.11, 2024.2.5)
Process completed with exit code 1.
Run pytest (3.12, 2024.3.3)
Process completed with exit code 1.
Run pytest (3.12, dev): core/tests/components/adaptive_lighting/test_switch.py#L1334
test_light_switch_in_specific_area AttributeError: 'NoneType' object has no attribute 'items'
Run pytest (3.12, dev): core/tests/components/adaptive_lighting/test_switch.py#L1567
test_proactive_adaptation_with_separate_commands AssertionError: ['test_context'] assert 1 == 2 + where 1 = len(['test_context'])
Run pytest (3.12, dev)
Process completed with exit code 1.
Run pytest (3.12, 2024.4.1): core/tests/components/adaptive_lighting/test_switch.py#L1335
test_light_switch_in_specific_area AttributeError: 'collections.OrderedDict' object has no attribute 'get_by_name'
Run pytest (3.12, 2024.4.1)
Process completed with exit code 1.
Run pytest (3.10, 2023.1.7)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.1.7)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.1.7)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2023.3.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.3.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.3.6)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2023.2.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.2.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.2.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2023.5.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.5.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.5.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.11.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.11.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.11.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.8.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.8.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.8.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2022.11.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2022.11.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2022.11.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.12.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.12.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.12.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2022.12.9)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2022.12.9)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2022.12.9)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.10.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.10.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.10.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.6.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.6.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.6.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2024.2.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2024.2.5)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2024.2.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2024.1.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2024.1.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2024.1.6)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.9.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.9.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.9.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.11, 2023.7.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.7.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.11, 2023.7.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2023.4.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.4.6)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.10, 2023.4.6)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.12, 2024.3.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, 2024.3.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, 2024.3.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.12, dev)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, dev)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, dev)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.12, 2024.4.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, 2024.4.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run pytest (3.12, 2024.4.1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run pytest (3.10, 2023.1.7)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2023.1.7)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2023.1.7)
### 2. Push or run action again. ###
Run pytest (3.10, 2023.1.7)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2023.1.7)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2023.1.7)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2023.3.6)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2023.3.6)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2023.3.6)
### 2. Push or run action again. ###
Run pytest (3.10, 2023.3.6)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2023.3.6)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2023.3.6)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2023.2.5)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2023.2.5)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2023.2.5)
### 2. Push or run action again. ###
Run pytest (3.10, 2023.2.5)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2023.2.5)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2023.2.5)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2023.5.4)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2023.5.4)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2023.5.4)
### 2. Push or run action again. ###
Run pytest (3.10, 2023.5.4)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2023.5.4)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2023.5.4)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.11.3)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.11.3)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.11.3)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.11.3)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.11.3)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.11.3)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.8.4)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.8.4)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.8.4)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.8.4)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.8.4)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.8.4)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2022.11.5)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2022.11.5)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2022.11.5)
### 2. Push or run action again. ###
Run pytest (3.10, 2022.11.5)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2022.11.5)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2022.11.5)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.12.4)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.12.4)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.12.4)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.12.4)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.12.4)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.12.4)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2022.12.9)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2022.12.9)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2022.12.9)
### 2. Push or run action again. ###
Run pytest (3.10, 2022.12.9)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2022.12.9)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2022.12.9)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.10.5)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.10.5)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.10.5)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.10.5)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.10.5)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.10.5)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.6.3)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.6.3)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.6.3)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.6.3)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.6.3)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.6.3)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2024.2.5)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2024.2.5)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2024.2.5)
### 2. Push or run action again. ###
Run pytest (3.11, 2024.2.5)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2024.2.5)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2024.2.5)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2024.1.6)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2024.1.6)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2024.1.6)
### 2. Push or run action again. ###
Run pytest (3.11, 2024.1.6)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2024.1.6)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2024.1.6)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.9.3)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.9.3)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.9.3)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.9.3)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.9.3)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.9.3)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.11, 2023.7.3)
### If tests fail, try these debug steps: ###
Run pytest (3.11, 2023.7.3)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.11, 2023.7.3)
### 2. Push or run action again. ###
Run pytest (3.11, 2023.7.3)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.11, 2023.7.3)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.11, 2023.7.3)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.10, 2023.4.6)
### If tests fail, try these debug steps: ###
Run pytest (3.10, 2023.4.6)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.10, 2023.4.6)
### 2. Push or run action again. ###
Run pytest (3.10, 2023.4.6)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.10, 2023.4.6)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.10, 2023.4.6)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.12, 2024.3.3)
### If tests fail, try these debug steps: ###
Run pytest (3.12, 2024.3.3)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.12, 2024.3.3)
### 2. Push or run action again. ###
Run pytest (3.12, 2024.3.3)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.12, 2024.3.3)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.12, 2024.3.3)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.12, dev)
### If tests fail, try these debug steps: ###
Run pytest (3.12, dev)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.12, dev)
### 2. Push or run action again. ###
Run pytest (3.12, dev)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.12, dev)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.12, dev)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###
Run pytest (3.12, 2024.4.1)
### If tests fail, try these debug steps: ###
Run pytest (3.12, 2024.4.1)
### 1. Replace '-qq' from .github/workflow/pytest.yaml. with '-v' for extra verbosity. ###
Run pytest (3.12, 2024.4.1)
### 2. Push or run action again. ###
Run pytest (3.12, 2024.4.1)
### 3. Check for any log messages in github actions resembling the following using CTRL+F ###
Run pytest (3.12, 2024.4.1)
### 5. add 'component'.'module' (without the '') from the above log into the 'required' list inside of 'test_dependencies.py' ###
Run pytest (3.12, 2024.4.1)
### 6. Try again! If more issues persist they should be easily solvable by reading the verbose logs now. ###