public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: auh@auh.yoctoproject.org
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [AUH] automake: upgrading to 1.16.3 FAILED	[thread overview]
Message-ID: <MADEUP.165272523675D8FE.5278@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *automake* to *1.16.3* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade automake -V 1.16.3
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1413 entries from dependency cache.
INFO: Extracting current version source...
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.49.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.2+snapshot-732f63b4251fdc4da9d4ef94f99de72e37ca2029"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "tmp-auh-upgrades:732f63b4251fdc4da9d4ef94f99de72e37ca2029"
workspace            = "master-next:afec39415be67b6985f0a0c3de041b4f302ffff3"

Initialising tasks...done.
Sstate summary: Wanted 5 Found 0 Missed 5 Current 15 (0% match, 75% complete)
NOTE: Executing Tasks
ERROR: Command '['rm', '-rf', '/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-e93f45uq/workdir/automake-1.16.2']' returned non-zero exit status 1.
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-e93f45uq/temp/log.do_unpack.31793
Log data follows:
| rm: cannot remove '/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-e93f45uq/workdir/automake-1.16.2': Directory not empty
| ERROR: Command '['rm', '-rf', '/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-e93f45uq/workdir/automake-1.16.2']' returned non-zero exit status 1.
NOTE: Tasks Summary: Attempted 71 tasks of which 66 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
ERROR: Extracting source for automake failed



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-12-20 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 14:15 auh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-15 16:42 [AUH] automake: upgrading to 1.16.3 FAILED auh
2021-02-16  8:24 auh
2021-01-15 12:30 auh
2020-12-15 19:23 auh

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.165272523675D8FE.5278@lists.openembedded.org \
    --to=auh@auh.yoctoproject.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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