Re: Nucleo f030r8 fails at QEMU Cortex M3 test
Hi,toggle quoted messageShow quoted text
There was an issue in how we re-run sanitycheck on failed tests (retry) to eliminate false positive due to heavy load and Qemu not being able to deal with that. This is now fixed.
From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...] On Behalf Of Paul Sokolovsky
Sent: Monday, August 14, 2017 11:25 AM
To: Maciej Dębski <maciej.debski@...>
Subject: Re: [Zephyr-devel] Nucleo f030r8 fails at QEMU Cortex M3 test
On Mon, 14 Aug 2017 11:31:44 +0200
Maciej Dębski <maciej.debski@...> wrote:
Hello,*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.
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 _______________________________________________
Zephyr-devel mailing list