-
Notifications
You must be signed in to change notification settings - Fork 2k
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
sys: model ecc, evtimer, pipe and shell_lock in kconfig #19636
Conversation
899de84
to
da83670
Compare
After a bit of digging I think I figured out why there is a hash mismatch for native and tests/sys/shell_lock. The problem is that Now, since we have the logic of enabling it by default if native also in the header file, and kconfig does not explicitly set it to 0, it would enable by default, even though we want it disabled... The possible solutions would be:
diff --git a/tests/sys/shell_lock/Makefile b/tests/sys/shell_lock/Makefile
index 78f8bdb5fd..f7e3ccfd88 100644
--- a/tests/sys/shell_lock/Makefile
+++ b/tests/sys/shell_lock/Makefile
@@ -10,11 +10,12 @@ USEMODULE += shell_lock_auto_locking
ifneq (1,$(TEST_KCONFIG))
CFLAGS += -DCONFIG_SHELL_LOCK_PASSWORD=\"password\"
CFLAGS += -DCONFIG_SHELL_LOCK_AUTO_LOCK_TIMEOUT_MS=7000
+endif
# This config defaults to 1 on native, such that pm_off() would be called as soon as
# shell_run_once is terminated in shell_run_forever. We do not want this behavior for this test.
CFLAGS += -DCONFIG_SHELL_SHUTDOWN_ON_EXIT=0
-endif
+
# test_utils_interactive_sync_shell assumes that the prompt is always '> ' which breaks
# with the password prompt of the shell_lock module which is different from the shell's prompt
|
da854bb
to
a667267
Compare
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.
Looks good to me. See above comment. Please squash / amend directly, my ACK remains valid.
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.
LGTM, if murdock is happy I think it is OK. ACK.
a667267
to
0ef40af
Compare
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
GitHub status checks took too long to complete, so bors is giving up. You can adjust bors configuration to have it wait longer if you like. |
19620: dist/tools/openocd: fix parsing of flash bank base r=aabadie a=maribu ### Contribution description Since [80fc9fabc66a0bc767467fa14c703e5a9f340cd3] the format of the `flash list` command changed to a more human readable multi-line variant. Technically, the change is white-space only. Still, the current approach of parsing them with awk, sed and cut doesn't like the new multi-line format. The parsing is now delegated into a python script that is compatible across OpenOCD versions. [80fc9fabc66a0bc767467fa14c703e5a9f340cd3]: openocd-org/openocd@80fc9fa 19636: sys: model ecc, evtimer, pipe and shell_lock in kconfig r=aabadie a=aabadie 19639: tests/net/gnrc_mac_timeout: add automated test r=aabadie a=aabadie Co-authored-by: Marian Buschsieweke <[email protected]> Co-authored-by: Alexandre Abadie <[email protected]>
Build failed (retrying...): |
diff --git a/tests/net/gnrc_netif/main.c b/tests/net/gnrc_netif/main.c
index 34fff1e905..caf86553e1 100644
--- a/tests/net/gnrc_netif/main.c
+++ b/tests/net/gnrc_netif/main.c
@@ -38,7 +38,6 @@
#include "net/netif.h"
#include "test_utils/expect.h"
#include "utlist.h"
-#include "xtimer.h"
#define ETHERNET_STACKSIZE (THREAD_STACKSIZE_MAIN)
#define IEEE802154_STACKSIZE (THREAD_STACKSIZE_MAIN) is required to fix the build failure for the waspmote-pro. (That board is fundamentally incompatible with xtimer. If |
bors cancel (The compilation issue with the waspmote-pro will cause this to fail again anyway, so let's take this out of the merge train for now.) |
Canceled. |
0ef40af
to
8b53e74
Compare
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
GitHub status checks took too long to complete, so bors is giving up. You can adjust bors configuration to have it wait longer if you like. |
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
19636: sys: model ecc, evtimer, pipe and shell_lock in kconfig r=aabadie a=aabadie Co-authored-by: Alexandre Abadie <[email protected]>
bors cancel |
Canceled. |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Contribution description
This PR also drops the xtimer backend from evtimer so simplify the Kconfig dependency modeling.
For
shell_lock
, I tried to expose some compile time configuration as Kconfig option but for some reason the automated test doesn't work with TEST_KCONFIG=1 on native. Some Kconfig expert help is appreciated for this one.I can split in smaller PRs of needed.
Testing procedure
Issues/PRs references
Tick some items in #16875