Extend the Bridle test environment #253
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This HAL is needed by Zephyr upstream boards to build the Bridle common test suite against all supported boards, the Zephyr and Bridle boards. Signed-off-by: Stephan Linz <[email protected]>
This HAL is needed by Zephyr upstream boards to build the Bridle common test suite against all supported boards, the Zephyr and Bridle boards. Signed-off-by: Stephan Linz <[email protected]>
This HAL is needed by Zephyr upstream test suite to build all sensor drivers. Signed-off-by: Stephan Linz <[email protected]>
To avoid potentially namespace conflicts on file system level all the `sample.yaml` and `testcase.yaml` files should have their own subfolder following the differentiation of Zephyr. Signed-off-by: Stephan Linz <[email protected]>
github-actions
bot
added
area: Boards
area: Documentation
area: Tests
area: Release Notes
labels
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
The new snippet for tests are:
|
To be able to control the Bridle common test suite not build over all boards a list of integration platforms must be there. Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all MFD drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/mfd` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream MFD drivers can be tested against the Zephyr upstream build-all MFD driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream) and additional nodes for: * MFD driver for a Maxim DS3231 device * MFD driver for a SIPO/MUX GP matrix Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all I2C drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/i2c` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream I2C drivers can be tested against the Zephyr upstream build-all I2C driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream). Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all UART drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/uart` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream UART drivers can be tested against the Zephyr upstream build-all UART driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream). Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all GPIO drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/gpio` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream GPIO drivers can be tested against the Zephyr upstream build-all GPIO driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream) and additional nodes for: * GPIO driver for a PCA9554, 8-bit I/O expander on I2C bus * GPIO driver for a PCA9555, 16-bit I/O expander on I2C bus * GPIO driver for a SIPO/MUX GP matrix Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all RTC drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/rtc` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream RTC drivers can be tested against the Zephyr upstream build-all RTC driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream) and additional nodes for: * RTC driver for a Maxim DS3231 device Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all Sensor drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/sensor` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream sensor drivers can be tested against the Zephyr upstream build-all sensor driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream) and additional nodes for: * Sensor driver for a Maxim DS3231 device (die temperature) Signed-off-by: Stephan Linz <[email protected]>
In preparation for our own test runs across all Display drivers, this new snippet is required. This allows using the Zephyr upstream test in `zephyr/tests/drivers/build_all/display` directly via an alternative test specification, only with a configuration specified by this new snippet and a customized devicetree. Signed-off-by: Stephan Linz <[email protected]>
With this alternative configuration the downstream display drivers can be tested against the Zephyr upstream build-all display driver test suite. This is the first integration with the current Zephyr upstream device tree (sync to downstream) and additional nodes for: * MIPI DBI devices with 16-bit shifted transfer (ILI9488) * Display driver for a SIPO/MUX GP matrix Signed-off-by: Stephan Linz <[email protected]>
Since Bridle is able to execute preselected test suites from Zephyr upstream the QA integration pipeline should do so. Signed-off-by: Stephan Linz <[email protected]>
Document that we have additional HAL modules from Zephyr upstream and we now able to execute Zephyr upstrem test suites for building all drivers together with our own snippets. Signed-off-by: Stephan Linz <[email protected]>
As we are preparing support for Zephyr 3.7 this bumps the Zephyr version to 3.7 following the 3.7 branch for bug fixes and security updates. Signed-off-by: Stephan Linz <[email protected]>
Respects our 3.7 development cycle, but Zephyr stable release. Signed-off-by: Stephan Linz <[email protected]>
Add 3.7.0-rc1 tag and 3.7 branch to release list to be shown on documentation side bar. Signed-off-by: Stephan Linz <[email protected]>
Add github issue resolved by the previous commits, bump to Zephyr v3.7. Signed-off-by: Stephan Linz <[email protected]>
1st release candidate 3.7.0 tag. Signed-off-by: Stephan Linz <[email protected]>
tobiaskaestner
approved these changes
Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With some more alternative test specifications for Twister, Bridle is now able to execute preselected test suites from Zephyr upstream together with the Bridle owned test suits and/or extensions.
This PR is important for PR #248 and #249.
Also resolves #254 (brand new).