From: auh@auh.yoctoproject.org
To: Ross Burton <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [AUH] vulkan-demos: upgrading to b9f0ac91d2adccc3055a904d3a8f6553b10ff6cd FAILED [thread overview]
Message-ID: <MADEUP.163E71D70FF81C70.13247@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3172 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-demos* to *b9f0ac91d2adccc3055a904d3a8f6553b10ff6cd* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-demos -S b9f0ac91d2adccc3055a904d3a8f6553b10ff6cd
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1506 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.47.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.1+snapshot-20201016"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:2d076d21137113760f34898162e1737b7ba4a340"
workspace = "master:ad30a6d470eca0f5be5c037ba37fad72e55a128c"
Initialising tasks...done.
Sstate summary: Wanted 0 Found 0 Missed 0 Current 20 (0% match, 100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting upgraded version source...
ERROR: Execution of 'git checkout b9f0ac91d2adccc3055a904d3a8f6553b10ff6cd' failed with exit code 1:
error: The following untracked working tree files would be overwritten by checkout:
external/ktx/LICENSE.md
external/ktx/NOTICE.md
external/ktx/README.md
external/ktx/include/ktx.h
external/ktx/include/ktxvulkan.h
external/ktx/lib/checkheader.c
external/ktx/lib/errstr.c
external/ktx/lib/etcdec.cxx
external/ktx/lib/etcunpack.cxx
external/ktx/lib/filestream.c
external/ktx/lib/filestream.h
external/ktx/lib/gl_format.h
external/ktx/lib/gl_funcptrs.h
external/ktx/lib/gles1_funcptrs.h
external/ktx/lib/gles2_funcptrs.h
external/ktx/lib/gles3_funcptrs.h
external/ktx/lib/glloader.c
external/ktx/lib/hashlist.c
external/ktx/lib/hashtable.c
external/ktx/lib/ktxgl.h
external/ktx/lib/ktxint.h
external/ktx/lib/libktx.gypi
external/ktx/lib/mainpage.md
external/ktx/lib/memstream.c
external/ktx/lib/memstream.h
external/ktx/lib/stream.h
external/ktx/lib/swap.c
external/ktx/lib/texture.c
external/ktx/lib/uthash.h
external/ktx/lib/vk_format.h
external/ktx/lib/vk_funclist.inl
external/ktx/lib/vk_funcs.c
external/ktx/lib/vk_funcs.h
external/ktx/lib/vkloader.c
external/ktx/lib/writer.c
external/ktx/lib/writer_v1.c
external/ktx/other_include/KHR/khrplatform.h
Please move or remove them before you switch branches.
Aborting
Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
reply other threads:[~2020-10-16 10:21 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=MADEUP.163E71D70FF81C70.13247@lists.openembedded.org \
--to=auh@auh.yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox