From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@01.org
Subject: Re: [LKP] [xarray] 93eb07f72c: RIP:__sanitizer_cov_trace_pc
Date: Fri, 14 Dec 2018 05:50:01 -0800 [thread overview]
Message-ID: <20181214135000.GA10600@bombadil.infradead.org> (raw)
In-Reply-To: <20181214083136.GB23332@shao2-debian>
On Fri, Dec 14, 2018 at 04:31:36PM +0800, kernel test robot wrote:
> initrds=(
> /osimage/quantal/quantal-core-x86_64-2018-11-09.cgz
> /lkp/lkp/lkp-x86_64.cgz
> /osimage/pkg/debian-x86_64-2016-08-31.cgz/trinity-static-x86_64-x86_64-6ddabfd2_2017-11-10.cgz
> )
>
> HTTP_PREFIX=https://download.01.org/0day-ci/lkp-qemu
> wget --timestamping "${initrds[@]/#/$HTTP_PREFIX}"
I love that you're providing this service, but seriously, this is the
third report in a row that's just wrong.
--2018-12-14 08:48:21-- https://download.01.org/0day-ci/lkp-qemu/osimage/quantal/quantal-core-x86_64-2018-11-09.cgz
Resolving download.01.org (download.01.org)... 104.90.64.218, 2600:1408:3000:28b::ae6, 2600:1408:3000:291::ae6
Connecting to download.01.org (download.01.org)|104.90.64.218|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-12-14 08:48:21 ERROR 404: Not Found.
--2018-12-14 08:48:21-- https://download.01.org/0day-ci/lkp-qemu/lkp/lkp/lkp-x86_64.cgz
Reusing existing connection to download.01.org:443.
HTTP request sent, awaiting response... 404 Not Found
2018-12-14 08:48:21 ERROR 404: Not Found.
prev parent reply other threads:[~2018-12-14 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 8:31 kernel test robot
2018-12-14 13:50 ` Matthew Wilcox [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=20181214135000.GA10600@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®