Hello Maciej,

On Mon, 14 Aug 2017 11:31:44 +0200
Maciej Dębski <maciej.debski@...> wrote:

Hello,

I just posted a pull request for my nucleo f030r8 support. Here it is:
https://github.com/zephyrproject-rtos/zephyr/pull/1103

The shippable ran all the tests correctly, just one with a failure,
which is:
*Sanitycheck / qemu_cortex_m3:tests/net/ieee802154/l2/test /
qemu_cortex_m3/tests/net/ieee802154/l2/test*

As far as I believe, this test is not related to my board. I am not
sure though. Could you give me some information on how I should react
to this? How can I correct this? What does the test mean? Is there a
way to not test my code with it?

*All* tests fail sooner or later, with or without a reason. (As Murphy
would add, non-tests fail sooner or later too.) If you're sure it's
random failure not related to your changes, then you just need to
resubmit your pull request to trigger a new CI build. To resubmit a PR,
its commit revisions should change. The easiest way to achieve that is
to rebase on the latest master. If it happens that nobody pushed any
new commits to master yet, then you can do something like:

git rebase --ignore-date HEAD^

This will update date of your last commit, thus changing its revision,
and will allow to force-push the PR as usual.

Thank you for help,
Maciej Dębski

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog