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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because tests now change between targets and toolchains, this really needs to be moved above the
build_tests
call inside the main build loop. Otherwise this will try to compile tests that aren't valid for certain combinations of targets and toolchains.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't
find_tests()
care of this? I just recently started looking at the build system and I'm not that familiar with general architecture but this seems to me good idea regarding separation of concern.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It used to be that this was the case. The tests that were ran were always the same for every target and toolchain. But now certain boards have certain "features" that other boards don't support. There could (and should) be tests under these feature folders that should only be built/tested if the board supports this feature. So this is why test discovery is now dependent on target and toolchain.