Skip to content

Sanitycheck shows "FAILED: failed" for successful test: tests/kernel/fifo/fifo_api/kernel.fifo #14586

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

Closed
mike-scott opened this issue Mar 15, 2019 · 4 comments
Assignees
Labels
area: Sanitycheck Sanitycheck has been renamed to Twister bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@mike-scott
Copy link
Contributor

Describe the bug
Occasionally in a sanitycheck run on real HW, we see the tests/kernel/fifo/fifo_api/kernel.fifo shown as "failed", but looking at the actual test log shows "PROJECT EXECUTION SUCCESSFUL"

CI Log for sanitycheck run on nrf52_blenano2: https://ci.foundries.io/projects/zephyr/builds/5367/sanity-test-nrf52/artifacts/console.log

To Reproduce
Hard to reproduce, but if you rinse and repeat the following sanitycheck command long enough you should see the failure described above:

sanitycheck --platform nrf52_blenano2 --inline-logs --outdir /tmp/outdir --enable-slow --verbose --no-clean --disable-size-report --load-tests /tmp/test-list --test-only --device-testing --device-serial /dev/ttyACM0 --west-flash=--board-id=109300003131a6610c36303333363445a5a5a5a597969906 -e kernel

Expected behavior
Test showing "PROJECT EXECUTION SUCCESSFUL" should not be called "FAILED".

Impact
CI inconsistency

Screenshots or console output
https://ci.foundries.io/projects/zephyr/builds/5367/sanity-test-nrf52/artifacts/console.log

Environment (please complete the following information):

  • OS: Linux
  • Toolchain: Zephyr SDK
  • Commit SHA or Version used: 6000a62
@mike-scott mike-scott added the bug The issue is a bug, or the PR is fixing a bug label Mar 15, 2019
@aescolar aescolar added the area: Sanitycheck Sanitycheck has been renamed to Twister label Mar 16, 2019
@nashif
Copy link
Member

nashif commented Mar 16, 2019

That log is not really useful, need the actual test log. Sometimes a test passes just fine but before it is terminated an exception happens which causes the failure..

@nashif nashif added the priority: low Low impact/importance bug label Mar 18, 2019
@nashif
Copy link
Member

nashif commented Mar 25, 2019

ping?

@nashif
Copy link
Member

nashif commented Mar 26, 2019

@mike-scott ping?

@nashif
Copy link
Member

nashif commented Mar 29, 2019

can't reproduce and no additional details.

@nashif nashif closed this as completed Mar 29, 2019
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 bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants