-
Notifications
You must be signed in to change notification settings - Fork 2.1k
kconfig explore all allowed boards on all apps #17595
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
Conversation
Well surprisingly things are looking very good. The only issue was with the ublox-c030-u201 makefile.dep modelling. I think it just wasn't done correctly. I removed it and added now think we can run all tests on all non-blocklisted boards for the nightlies. I added a removeme commit to test if the nightly flag would actually run it properly. |
This shows that the
|
Before removing the "REMOVEME" commit, it would be nice to complete the review as it will delete the link indicating nightly does actually perform the tests. Of course, I squash, rebase, and remove the commit, it should indicate that the ublox board is not tested. ping @leandrolanzieri @fjmolinas or @kaspar030 |
Can you explain a bit more what 51c3062 commit is doing? |
I guess it is easier to look at it after the fixup. This was my initial commit that removed the |
Makes sense, I checked that the test was run, inlined the result in your comments as well. Please squash @MrKevinWeiss! |
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.
ACK
f50dee7
to
35d4eda
Compare
Let me just post a link to the test result from murdock before we merge. |
Here we can see the test did not check kconfig, which is expected as the nightly flag is removed.... It seems like I left a whitespace in so I will have to rerun again after force pushing. I will paste the output so it isn't lost
|
This modelling doesn't seem correct and probably shouldn't be in here. Normally vfs modelling shouldn't be handled in the boards. Even if it was the mtd modelling is also not correct.
35d4eda
to
514ea77
Compare
Contribution description
Run all non-blockisted boards for every kconfig enabled app only during nightlies.
This should find any corner cases slipping through the regular testing (currently only one on the ublox-c030-u201 board due to incorrect makefile modelling). This should also have no impact on regular CI times, only the nightly will be longer (since it will eventually double the jobs).
Testing procedure
Check to see that the removeme commit, forcing nightly, tests a board that would not normally be tested for kconfig.
Issues/PRs references