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

test/msg_send_receive: fails on samr21-xpro #5699

Closed
BytesGalore opened this issue Jul 27, 2016 · 11 comments
Closed

test/msg_send_receive: fails on samr21-xpro #5699

BytesGalore opened this issue Jul 27, 2016 · 11 comments
Assignees
Labels
Area: tests Area: tests and testing framework Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@BytesGalore
Copy link
Member

Found during release 2016.07 testing RIOT-OS/Release-Specs#24 (comment)
The test fails on samr21-xpro board because of a wrong value present in msg_resp.content.ptr in the last iteration.
Printing the values of counter and msg_resp.content.ptr (resp val) for each iteration revealed:

# main(): This is RIOT! (Version: 2013.08-10643-gb5cb6-user01-LLED-E6410)
# Incremented counters to 1 and 1
# resp val: 1, counter: 1

... all ok until the last one:

# Incremented counters to 10 and 10
# resp val: 841, counter: 10
# Test failed.
@BytesGalore BytesGalore added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: tests Area: tests and testing framework labels Jul 27, 2016
@BytesGalore BytesGalore changed the title test/msg_send_receive: fials on samr21-xpro test/msg_send_receive: fails on samr21-xpro Jul 27, 2016
@kYc0o
Copy link
Contributor

kYc0o commented Jul 27, 2016

any hint @kaspar030 ?

@OlegHahm
Copy link
Member

Try to revert #5444

@BytesGalore
Copy link
Member Author

@OlegHahm reverting #5444 didn't help

@OlegHahm
Copy link
Member

Have you tested on other platforms?

@BytesGalore
Copy link
Member Author

on native -> works, i.e. success

@kaspar030
Copy link
Contributor

Looks to me like the threads are sending around pointers to their stacks, and in the last iteration, one of the threads already exited.

Could you try to add thread_sleep() before the return in thread2()?

@BytesGalore
Copy link
Member Author

@kaspar030 that did it

@BytesGalore
Copy link
Member Author

(I mean the test succeeds now)

@kaspar030
Copy link
Contributor

I'll prepare a PR.

@BytesGalore
Copy link
Member Author

nice

@kaspar030
Copy link
Contributor

#5701

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: tests Area: tests and testing framework Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

4 participants