This is a CI issue. We just need to restart it manually. Maybe we could add some tests to retry automatically when errors like this happen.
On 11/26/22, TimH <t...@jti.uk.com.invalid> wrote: > Thanks for the support - another 2 PRs submitted now. > > But one failed tests with multiple instances of: > > " Error: Error response from daemon: login attempt to https://ghcr.io/v2/ > failed with status: 503 Service Unavailable" > > Do I need to do anything to get the tests to rerun and hopefully pass? > >>-----Original Message----- >>From: Tim Hardisty <t...@hardisty.co.uk> >>Sent: 25 November 2022 14:46 >>To: dev@nuttx.apache.org >>Subject: Apologies >> >>Some may have seen I've been attempting multiple times to submit PRs for 2 >>issues (SAMA5D2 related) and have closed/cancelled/retried numerous >>times. >> >>Bottom line - I am struggling with the whole rebase/squash/merge >> cycle...as >>I'm a complete numpty. Code I can mostly do, but this is the first time > working >>with a public repo not just my with own private code where I can do > whatever >>I want ;) >> >>I will fully "get it", eventually, but have now, at long last, had my >> first > actual >>code PR accepted and merged. Thank you for your understanding and >>patience! >> >>Regards, >> >>TimJTi >>--------------------------------------- >>PS I believe any email sent to the mail reflector that has been DKIM >> signed > will >>end up in recipients spam folder...hence sending this from a non-DKIM > signed >>email account to see what happens. > >
