Skip to content

.murdock: Kconfig test apps for all boards #17402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 15, 2021

Conversation

MrKevinWeiss
Copy link
Contributor

Contribution description

Introduce the TEST_KCONFIG_TEST_ALLOWLIST and TEST_KCONFIG_BOARD_BLOCKLIST
This will test kconfig modeling on a small subset of apps
for all boards that are not on the blocklist.

This should automatically test new boards, preventing merging
of non-kconfig complete boards.

Testing procedure

CI green and verify that boards are being tested by murdock for the specified apps.

Issues/PRs references

Part of #16875

@MrKevinWeiss MrKevinWeiss added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Area: Kconfig Area: Kconfig integration labels Dec 15, 2021
@MrKevinWeiss MrKevinWeiss self-assigned this Dec 15, 2021
@github-actions github-actions bot added Area: CI Area: Continuous Integration of RIOT components and removed Area: Kconfig Area: Kconfig integration labels Dec 15, 2021
.murdock Outdated
@@ -425,7 +471,9 @@ compile() {

if [ ${should_check_kconfig_hash} != 0 ]; then
if [ ${kconfig_test_hash} != ${test_hash} ]; then
tput setaf 1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this do?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh this is just temporary, when I run in my console it shows this warning in red, easier to scan while things are going. Please ignore.

@kaspar030
Copy link
Contributor

LGTM.

@MrKevinWeiss
Copy link
Contributor Author

These tests seem to be working. I think there are still some low hanging fruit boards but maybe we should get this in first and remove them later. May I squash and clean?

@kaspar030
Copy link
Contributor

kaspar030 commented Dec 15, 2021

Yes, please squash!

Introduce the TEST_KCONFIG_TEST_ALLOWLIST and TEST_KCONFIG_BOARD_BLOCKLIST
This will test kconfig modeling on a small subset of apps
for all boards that are not on the blocklist.

This should automatically test new boards, preventing merging
of non-kconfig complete boards.
@MrKevinWeiss
Copy link
Contributor Author

Squashed, removed app limiting, and cleaned up the tput commands. Everything should be good to go. As we have to wait for the CI maybe now would be a good time to auto-merge?

@MrKevinWeiss MrKevinWeiss added Area: Kconfig Area: Kconfig integration CI: full build disable CI build filter labels Dec 15, 2021
@kaspar030 kaspar030 enabled auto-merge December 15, 2021 17:55
@MrKevinWeiss
Copy link
Contributor Author

Many thanks for the quick reviews, it is nice to get this in before everyone's vacation.

@MrKevinWeiss
Copy link
Contributor Author

Oh shoot, we need an ack ping @kaspar030 @fjmolinas

Copy link
Contributor

@fjmolinas fjmolinas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK!

@kaspar030 kaspar030 merged commit 6efee52 into RIOT-OS:master Dec 15, 2021
@MrKevinWeiss MrKevinWeiss deleted the pr/ci/testallboards branch December 16, 2021 08:31
@fjmolinas fjmolinas added this to the Release 2022.01 milestone Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: CI Area: Continuous Integration of RIOT components Area: Kconfig Area: Kconfig integration CI: full build disable CI build filter CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants