twister: rework board enumeration #77250
Open
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
nashif
force-pushed
the
topic/twister/board_def_3
branch
2 times, most recently
from
5e1b8b1
to
eb5060d
Compare
ithinuel
reviewed
Aug 21, 2024
boards/arm/fvp_base_revc_2xaemv8a/fvp_base_revc_2xaemv8a_fvp_base_revc_2xaemv8a_smp_ns.yaml
Show resolved
Hide resolved
nashif
force-pushed
the
topic/twister/board_def_3
branch
2 times, most recently
from
7a31de9
to
f4aa094
Compare
nashif
force-pushed
the
topic/twister/board_def_3
branch
2 times, most recently
from
fd66817
to
759726a
Compare
|
adapted all tests and fixed many issues discovered by the twister testsuite... |
|
@gchwier @golowanow @PerMac @LukaszMrugala @hakehuang please review. it is still in early draft with many cleanups to be done, but the basic functionality is working. |
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
759726a
to
31aee86
Compare
|
can we have a yaml processing script that can auto merge yaml files that are impacted to twister.yaml? |
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
31aee86
to
39b15de
Compare
we can, for majority of boards this will not be needed as it means a simple rename only though. |
zephyrbot
added
area: ARM64
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
39b15de
to
5c4a596
Compare
zephyrbot
added
area: Continuous Integration
area: Coding Guidelines
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
5c4a596
to
ee59730
Compare
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
ee59730
to
04ce675
Compare
We now use hwmv2 to list boards instead of relying on twister specific config files. One yaml files (twister.yaml for now) will have all the data needed for all possible targets and variations of a board reusing most of the data where possible and variations can override the top level data. Twister keeps track of 'aliases' of boards and identifies that for example native_sim is the same as native_sim/native, so either names will be possible in both test yaml files or on the command line, however, the reporting will always use the full name, so no there is no confusion about what is being tested/built. Signed-off-by: Anas Nashif <[email protected]>
Use twister.yaml and fix revisions in board.yml. Signed-off-by: Anas Nashif <[email protected]>
Use one single twister configuration file. Signed-off-by: Anas Nashif <[email protected]>
Updated tests for new board handling. Signed-off-by: Anas Nashif <[email protected]>
configure revisions in board.yml file. Signed-off-by: Anas Nashif <[email protected]>
Do not use shortcuts... Signed-off-by: Anas Nashif <[email protected]>
no shortcuts allowed in test files Signed-off-by: Anas Nashif <[email protected]>
nashif
force-pushed
the
topic/twister/board_def_3
branch
from
04ce675
to
ae303ae
Compare
nashif
added a commit
to nashif/zephyr
that referenced
this pull request
Oct 4, 2024
Full name or description of a board is something we are missing in HWVv2. It is right now being added to yaml files parsed by twister. This should be generically available to tooling and documentation independently from twister. As we rework how twister parses board meta-data (zephyrproject-rtos#77250) and how we generate board documentation (zephyrproject-rtos#79160), this becomes neceassry. Moving the board full name/description from the twister yaml files to the board.yaml is something we can automate once the schema is agreed upon. Signed-off-by: Anas Nashif <[email protected]>
nashif
added a commit
to nashif/zephyr
that referenced
this pull request
Oct 4, 2024
Full name or description of a board is something we are missing in HWVv2. It is right now being added to yaml files parsed by twister. This should be generically available to tooling and documentation independently from twister. As we rework how twister parses board meta-data (zephyrproject-rtos#77250) and how we generate board documentation (zephyrproject-rtos#79160), this becomes neceassry. Moving the board full name/description from the twister yaml files to the board.yaml is something we can automate once the schema is agreed upon. Signed-off-by: Anas Nashif <[email protected]>
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.
We now use hwmv2 to list boards instead of relying on twister specific
config files.
One yaml file (twister.yaml for now) will have all the data needed for
all possible targets and variations of a board reusing most of the data
where possible and variations can override the top level data.
Twister keeps track of 'aliases' of boards and identifies that for
example native_sim is the same as native_sim/native, so either names
will be possible in both test yaml files or on the command line,
however, the reporting will always use the full name, so no there is no
confusion about what is being tested/built.
Fixes #74142