Skip to content
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

sanitycheck incorrect judgement with tests/drivers/gpio/gpio_basic_api. #24661

Closed
chen-png opened this issue Apr 24, 2020 · 0 comments · Fixed by #24953
Closed

sanitycheck incorrect judgement with tests/drivers/gpio/gpio_basic_api. #24661

chen-png opened this issue Apr 24, 2020 · 0 comments · Fixed by #24953
Assignees
Labels
area: Sanitycheck Sanitycheck has been renamed to Twister area: Test Framework Issues related not to a particular test, but to the framework instead bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Comments

@chen-png
Copy link
Collaborator

chen-png commented Apr 24, 2020

Describe the bug
after connecting gpio pins according to readme file, the tests/drivers/gpio/gpio_basic_api/ is passed, but it would be judges as failed by sanitycheck script.

it occurred on frdm_k64f, sam_e70_xplained, mimxrt1050_evk board.

To Reproduce

  1. used west to build, it could get the "project execution successful" from serial.
  2. ran this test using sanitycheck alone, it also was passed.
  3. but if ran the whole tests directory using sanitycheck, this test was always judged as failed.

Screenshots or console output

could see the test output in hander.log and it was successful, but it was judged as failed

drivers.gpio.2pin
frdm_k64f:drivers.gpio.2pin
Time Taken: 29.259097s
Failed: failed


*** Booting Zephyr OS build zephyr-v2.2.0-1885-gb7897d5aab13  ***
Running test suite gpio_basic_test

starting test - test_gpio_port
Validate device GPIO_2
Check GPIO_2 output 16 connected to input 17
OUT 16 to IN 17 linkage works
- bits_physical
- pin_physical
- check_raw_output_levels
- check_logic_output_levels
- check_input_levels
- bits_logical
- check_pulls
NOTE: cannot configure pin as disconnected; trying as input
PASS - test_gpio_port

starting test - test_gpio_callback_add_remove
callback_2 triggered: 1
callback_1 triggered: 1
callback_2 triggered: 1
PASS - test_gpio_callback_add_remove

starting test - test_gpio_callback_self_remove
callback_remove_self triggered: 1
callback_1 triggered: 1
callback_1 triggered: 1
PASS - test_gpio_callback_self_remove

starting test - test_gpio_callback_enable_disable
callback_2 triggered: 1
callback_1 triggered: 1
callback_2 triggered: 1
callback_1 triggered: 1
PASS - test_gpio_callback_enable_disable

starting test - test_gpio_callback_variants
callback triggered: 1
OUT init a01, IN cfg 34000, cnt 1
callback triggered: 1
OUT init 600, IN cfg 54000, cnt 1
callback triggered: 1
OUT init 600, IN cfg 5c000, cnt 1
callback triggered: 1
OUT init a01, IN cfg 3c000, cnt 1
callback triggered: 1
callback triggered: 2
callback triggered: 3
OUT init 600, IN cfg 44000, cnt 3
callback triggered: 1
callback triggered: 2
callback triggered: 3
OUT init a01, IN cfg 24000, cnt 3
callback triggered: 1
callback triggered: 2
callback triggered: 3
OUT init 600, IN cfg 4c000, cnt 3
callback triggered: 1
callback triggered: 2
callback triggered: 3
OUT init a01, IN cfg 2c000, cnt 3
callback triggered: 1
callback triggered: 2
OUT init a01, IN cfg 74000, cnt 2
PASS - test_gpio_callback_variants

starting test - test_gpio_deprecated
callback triggered: 1
INT cfg 50000, cnt 1
callback triggered: 1
INT cfg 30000, cnt 1
callback triggered: 1
callback triggered: 2
INT cfg 74000, cnt 2
callback triggered: 1
callback triggered: 2
callback triggered: 3
INT cfg 40000, cnt 3
callback triggered: 1
callback triggered: 2
callback triggered: 3
INT cfg 20000, cnt 3
PASS - test_gpio_deprecated

Test suite gpio_basic_test succeeded

**PROJECT EXECUTION SUCCESSFUL**

Environment (please complete the following information):

  • OS: fedora28
  • Toolchain: zephyr-sdk-0.11.2
  • Commit ID: b7897d5
@chen-png chen-png added the bug The issue is a bug, or the PR is fixing a bug label Apr 24, 2020
@carlescufi carlescufi added area: Sanitycheck Sanitycheck has been renamed to Twister priority: medium Medium impact/importance bug labels Apr 28, 2020
@carlescufi carlescufi added the area: Test Framework Issues related not to a particular test, but to the framework instead label Apr 30, 2020
nashif added a commit to nashif/zephyr that referenced this issue May 4, 2020
harness being set without actual use of harness (via harness_config)
makes the test behave differently.

Fixes zephyrproject-rtos#24661

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
nashif added a commit that referenced this issue May 5, 2020
harness being set without actual use of harness (via harness_config)
makes the test behave differently.

Fixes #24661

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
hakehuang pushed a commit to hakehuang/zephyr that referenced this issue Jun 20, 2020
harness being set without actual use of harness (via harness_config)
makes the test behave differently.

Fixes zephyrproject-rtos#24661

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Sanitycheck Sanitycheck has been renamed to Twister area: Test Framework Issues related not to a particular test, but to the framework instead bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants