From: David Howells <dhowells@redhat.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: dhowells@redhat.com, oe-lkp@lists.linux.dev, lkp@intel.com,
Steve French <sfrench@samba.org>,
Shyam Prasad N <nspmangalore@gmail.com>,
"Rohith Surabattula" <rohiths.msft@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org
Subject: Re: [dhowells-fs:cifs-netfs] [cifs] b4834f12a4: WARNING:at_fs/netfs/write_collect.c:#netfs_writeback_lookup_folio
Date: Fri, 26 Apr 2024 10:04:49 +0100 [thread overview]
Message-ID: <2146096.1714122289@warthog.procyon.org.uk> (raw)
In-Reply-To: <Zin4G2VYUiaYxsKQ@xsang-OptiPlex-9020>
Okay I got it to install somehow by moving tmp-pkg to pkg, running lkp
install (which failed), then moving it back and running lkp install again,
which succeeded.
Running lkp split-job gives me:
/root/lkp-tests/lib/erb.rb:35: warning: Passing safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and specify other arguments as keyword arguments.
/root/lkp-tests/lib/erb.rb:35: warning: Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, trim_mode: ...) instead.
/root/lkp-tests/lib/erb.rb:35: warning: Passing safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and specify other arguments as keyword arguments.
/root/lkp-tests/lib/erb.rb:35: warning: Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, trim_mode: ...) instead.
job.yaml => ./job-performance-1HDD-btrfs-cifs-filemicro_seqwriterandvargam.f-b4834f12a4df607aaedc627fa9b93f3b18f664ba-debian-12-x86_64-20240206.cgz.yaml
It looks like some of the Ruby scripting is out of date.
David
next prev parent reply other threads:[~2024-04-26 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 4:42 [dhowells-fs:cifs-netfs] [cifs] b4834f12a4: WARNING:at_fs/netfs/write_collect.c:#netfs_writeback_lookup_folio kernel test robot
2024-04-17 12:18 ` David Howells
2024-04-25 6:28 ` Oliver Sang
2024-04-26 8:34 ` David Howells
2024-04-26 8:52 ` David Howells
2024-04-26 8:56 ` David Howells
2024-04-26 9:04 ` David Howells [this message]
2024-04-26 9:42 ` David Howells
2024-04-26 10:59 ` Philip Li
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=2146096.1714122289@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=nspmangalore@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rohiths.msft@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.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;
as well as URLs for NNTP newsgroup(s).