From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: Buildbot kernel build rpm error
Date: Wed, 14 Apr 2021 15:38:24 -0500 [thread overview]
Message-ID: <CAH2r5mtnRaESzGuZf+J89H+G6FdF-dPfJxqURGLT2G4H3FZR4w@mail.gmail.com> (raw)
Any ideas why every other build of the kernel (for the buildbot
automated testing) fails with this (even if no code changed):
See e.g. http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/569
(and every other test run before that in last few days)
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-5.12.0_rc7-1.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-headers-5.12.0_rc7-1.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1YI7Dw
+ umask 022
+ cd .
+ rm -rf /root/rpmbuild/BUILDROOT/kernel-5.12.0_rc7-1.x86_64
+ exit 0
[*] stored new cache build
/tmp/kbuildcache/148df99b5d245d132a1fba07a172097721299031be12e092d324a1c02fcd68f5
[*] removing old cache entry
/tmp/kbuildcache/9bbac9f327189cbe0e7ab4816965528b82ac537e1f2b5267d139ef874f48874f
Traceback (most recent call last):
File "/root/buildbot/scripts/kernel-cache", line 117, in <module>
main()
File "/root/buildbot/scripts/kernel-cache", line 37, in main
cache.add_cache(args.rev, args.config, args.files)
File "/root/buildbot/scripts/kernel-cache", line 92, in add_cache
shutil.rmtree(e)
File "/usr/lib64/python3.6/shutil.py", line 477, in rmtree
onerror(os.lstat, path, sys.exc_info())
File "/usr/lib64/python3.6/shutil.py", line 475, in rmtree
orig_st = os.lstat(path)
TypeError: lstat: path should be string, bytes or os.PathLike, not tuple
Repeating the build it works (this seems new to 5.12-rc7)
--
Thanks,
Steve
reply other threads:[~2021-04-14 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAH2r5mtnRaESzGuZf+J89H+G6FdF-dPfJxqURGLT2G4H3FZR4w@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.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).