From: Li Zhijian <zhijianx.li@intel.com>
To: Matthew Wilcox <willy@infradead.org>,
kernel test robot <rong.a.chen@intel.com>
Cc: 0day robot <lkp@intel.com>, Jens Axboe <axboe@kernel.dk>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [LKP] Re: [pipe] f2af7d90e2: xfstests.btrfs.052.fail
Date: Mon, 11 May 2020 12:06:20 +0800 [thread overview]
Message-ID: <b6cb98f4-4265-b518-f692-d56d3fb1cad5@intel.com> (raw)
In-Reply-To: <20200511011601.GV16070@bombadil.infradead.org>
Hi Matthew
with a quick look into the dmesg
looks this commit broke the preparation of LKP tests
[ 32.677588] install debs round two: dpkg -i --force-confdef
--force-depends /opt/deb/gawk_1%3a4.1.4+dfsg-1_amd64.deb
[ 32.677593]-
[ 32.697180] tar: ./control: Cannot write: Invalid argument
[ 32.697184]-
[ 32.705025] tar: ./md5sums: Cannot write: Invalid argument
[ 32.705030]-
[ 32.710034] tar: ./postinst: Cannot write: Invalid argument
[ 32.710039]-
[ 32.743721] tar: ./prerm: Cannot write: Invalid argument
i tried apt command, it also failed with this commit
root@vm-snb-186 ~# apt update
Ign:1 http://linux-ftp.sh.intel.com/pub/mirrors/debian stretch InRelease
Get:2 http://linux-ftp.sh.intel.com/pub/mirrors/debian testing InRelease
[116 kB]
Ign:2 http://linux-ftp.sh.intel.com/pub/mirrors/debian testing InRelease
Get:3 http://linux-ftp.sh.intel.com/pub/mirrors/debian unstable
InRelease [146 kB]
Ign:3 http://linux-ftp.sh.intel.com/pub/mirrors/debian unstable InRelease
Get:4 http://linux-ftp.sh.intel.com/pub/mirrors/debian stretch Release
[118 kB]
Err:4 http://linux-ftp.sh.intel.com/pub/mirrors/debian stretch Release
Error writing to output file - write (22: Invalid argument)
Get:5 http://linux-ftp.sh.intel.com/pub/mirrors/debian testing Release
[115 kB]
Err:5 http://linux-ftp.sh.intel.com/pub/mirrors/debian testing Release
Error writing to output file - write (22: Invalid argument)
Get:6 http://linux-ftp.sh.intel.com/pub/mirrors/debian unstable Release
[145 kB]
Get:7 http://linux-ftp.sh.intel.com/pub/mirrors/debian unstable
Release.gpg [1601 B]
Err:7 http://linux-ftp.sh.intel.com/pub/mirrors/debian unstable Release.gpg
Error writing to output file - write (22: Invalid argument)
Reading package lists... Done
E: The repository 'http://linux-ftp.sh.intel.com/pub/mirrors/debian
stretch Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'http://linux-ftp.sh.intel.com/pub/mirrors/debian
testing Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'http://linux-ftp.sh.intel.com/pub/mirrors/debian
unstable Release' is not signed.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
everything works well without f2af7d90e2 in our environment
Thanks
On 5/11/20 9:16 AM, Matthew Wilcox wrote:
> On Mon, May 11, 2020 at 09:09:57AM +0800, kernel test robot wrote:
>> --- tests/btrfs/095.out 2020-04-09 10:45:28.000000000 +0800
>> +++ /lkp/benchmarks/xfstests/results//btrfs/095.out.bad 2020-05-06 21:13:51.276485703 +0800
>> @@ -1,35 +1,9 @@
>> QA output created by 095
>> -Blocks modified: [135 - 164]
>> -Blocks modified: [768 - 792]
>> +awk: line 19: function strtonum never defined
>> +awk: line 19: function strtonum never defined
>> +awk: line 19: function strtonum never defined
>> +awk: line 19: function strtonum never defined
> This looks like a problem with the test setup.
> _______________________________________________
> LKP mailing list -- lkp@lists.01.org
> To unsubscribe send an email to lkp-leave@lists.01.org
next prev parent reply other threads:[~2020-05-11 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 1:09 kernel test robot
2020-05-11 1:16 ` Matthew Wilcox
2020-05-11 1:36 ` Rong Chen
2020-05-11 4:06 ` Li Zhijian [this message]
2020-05-11 15:11 ` [LKP] " Jens Axboe
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=b6cb98f4-4265-b518-f692-d56d3fb1cad5@intel.com \
--to=zhijianx.li@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=rong.a.chen@intel.com \
--cc=willy@infradead.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®