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
occasional sanitycheck failures in samples/subsys/settings #26961
Comments
still seeing this, although with recent sanitycheck fixes this reports "Timeout" and not "Unexpected EOF" |
What does the |
It's a bash alias on my workstations equivalent to:
|
By the way I linked the wrong bug earlier, it's possible this is an instance of or related to #26949 |
I have run the command altering it a little bit: After ~2h of run I have not faced the issue. In my case |
I believe not, regex is ok and console output looks fine to me (match regex). What I saw at the beginning of the output there is 0x1B character which is
Is this might be an issue here? |
This is always printed by the emulated firmware. |
Anyway - looks like this is not settings or its test issue but test infrastructure issue. |
@andrewboie We were totally unable to reproduce occasional failure you had reported. This tests also is passing all the time on buldkite we are using here, eg.: https://buildkite.com/zephyr/zephyr/builds/7718#e2d59170-240c-40aa-b1ec-34e91454c193 Can we close this issue? |
I just reproduced this today.
|
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Might be a problem with the regexes used? The handler.log looks normal:
I have also seen this fail with truncated output in handler.log which I suspect may be an instance of #24649
The text was updated successfully, but these errors were encountered: