All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] meta-oe: add selftest for sources.oe.org
Date: Wed, 21 Nov 2018 07:38:07 -0700	[thread overview]
Message-ID: <31956b4f-337e-82da-b7dc-ee8ff54ce80d@gmail.com> (raw)
In-Reply-To: <CA+chaQcWFxnFZDUpxS1zsi7RCRwXecZBqCvxqj6G2tThSpZfxg@mail.gmail.com>

Thanks Martin,

Looks like this is the only failure left.

Summary: 1 task failed:
 
virtual:native:/home/build/releases/master/openembedded-core/meta/recipes-support/lz4/lz4_1.8.2.bb:do_fetch

- Armin



On 11/21/18 7:18 AM, Martin Jansa wrote:
> I've fixed known_hosts on abaco and some archives were finally rsynced:
> http://jenkins.nas-admin.org/view/OE/job/oe_world_workspace-rsync/481/console
>
> but it doesn't seem to cover all found issues, please re-run the test to
> see what's left.
>
>
> On Tue, Nov 20, 2018 at 9:07 AM Martin Jansa <martin.jansa@gmail.com> wrote:
>
>> The jenkins job which does the rsync (or at least how I was doing it), is
>> still failing as reported before:
>>
>> http://jenkins.nas-admin.org/view/OE/job/oe_world_workspace-rsync/480/console
>>
>> Either you're using something else now, or it still won't work.
>>
>> Regards,
>>
>> On Mon, Nov 19, 2018 at 9:18 PM Khem Raj <raj.khem@gmail.com> wrote:
>>
>>> Thanks Michael for taking care of it
>>>
>>> On Mon, Nov 19, 2018 at 12:02 PM Michael Halstead <
>>> mhalstead@linuxfoundation.org> wrote:
>>>
>>>> The rsync target on on the world build machine was offline following a
>>>> reboot causing the sync to sources.oe.org to fail. The rsync target is
>>> now
>>>> configured to be available following reboots and the sync has run.
>>> Please
>>>> let me know if this test still fails.
>>>>
>>>> On Wed, Nov 14, 2018 at 8:19 AM akuster808 <akuster808@gmail.com>
>>> wrote:
>>>>> --
>>>>> _______________________________________________
>>>>> Openembedded-devel mailing list
>>>>> Openembedded-devel@lists.openembedded.org
>>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>>
>>> --
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>



      reply	other threads:[~2018-11-21 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 22:40 [meta-oe][PATCH] meta-oe: add selftest for sources.oe.org Armin Kuster
2018-11-13 22:55 ` Martin Jansa
2018-11-13 23:27   ` akuster808
2018-11-14 15:17     ` Martin Jansa
2018-11-14 16:18       ` akuster808
2018-11-19 20:01         ` Michael Halstead
2018-11-19 20:18           ` Khem Raj
2018-11-20  8:07             ` Martin Jansa
2018-11-21 14:18               ` Martin Jansa
2018-11-21 14:38                 ` akuster808 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31956b4f-337e-82da-b7dc-ee8ff54ce80d@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.