[riot-notifications] [RIOT-OS/RIOT] sys/xtimer: improve spin define handling/documentation (#11546)

Gaëtan Harter notifications at github.com
Mon May 20 17:22:41 CEST 2019


I am currently running `tests/posix_semaphore tests/posix_time tests/pthread_barrier tests/pthread_cleanup tests/pthread_condition_variable tests/pthread_cooperation tests/pthread_rwlock tests/pthread_tls tests/xtimer_drift tests/xtimer_hang tests/xtimer_longterm tests/xtimer_msg tests/xtimer_msg_receive_timeout tests/xtimer_now64_continuity tests/xtimer_periodic_wakeup tests/xtimer_remove tests/xtimer_reset tests/xtimer_usleep tests/xtimer_usleep_short` tests on some boards.

I see this already breaks some `arduino-mega2560` tests.

* `tests/xtimer_periodic_wakeup` that gets stuck around `2019-05-20 17:06:38,792 - INFO # Testing interval 107... (now=5915664)`.
* `tests/xtimer_usleep` but was already broken since `stdio_uart_rx`
* `tests/xtimer_usleep_short` `2019-05-20 17:09:06,204 - INFO # going to sleep 90 usecs...
xtimer stuck when trying to sleep 90 usecs`

I will give more update on broken tests when I have results.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11546#issuecomment-494033710
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190520/b2e122da/attachment.html>


More information about the notifications mailing list