New issue
Advanced search Search tips

Issue 891528 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

fizz-release: failed to emerge sys-devel/libtool-2.4.6-r6: Cannot find the latest automake!

Project Member Reported by apronin@google.com, Oct 2

Issue description

build_packages on fizz-release failed for R71-11121.0.0 (http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8933755003430664864):


libtool-2.4.6-r6: >>> Preparing source in /build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/work/libtool-2.4.6 ...
  libtool-2.4.6-r6:  * Applying libtool-2.4.3-use-linux-version-in-fbsd.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-link-specs.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-link-fsanitize.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-link-fuse-ld.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-libtoolize-slow.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-libtoolize-delay-help.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-sed-quote-speedup.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-ppc64le.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-mint.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.2.6a-darwin-module-bundle.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-darwin-use-linux-version.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Applying libtool-2.4.6-clang-libs.patch ...
  libtool-2.4.6-r6:  [ ok ]
  libtool-2.4.6-r6:  * Running eautoreconf in '/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/work/libtool-2.4.6/libltdl' ...
  libtool-2.4.6-r6: Traceback (most recent call last):
  libtool-2.4.6-r6:   File "/usr/lib/portage/python2.7/ebuild-ipc.py", line 282, in <module>
  libtool-2.4.6-r6:     sys.exit(ebuild_ipc_main(sys.argv[1:]))
  libtool-2.4.6-r6:   File "/usr/lib/portage/python2.7/ebuild-ipc.py", line 279, in ebuild_ipc_main
  libtool-2.4.6-r6:     return ebuild_ipc.communicate(args)
  libtool-2.4.6-r6:   File "/usr/lib/portage/python2.7/ebuild-ipc.py", line 136, in communicate
  libtool-2.4.6-r6:     lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  libtool-2.4.6-r6:   File "/usr/lib64/python2.7/site-packages/portage/locks.py", line 113, in lockfile
  libtool-2.4.6-r6:     raise PermissionDenied(func_call)
  libtool-2.4.6-r6: portage.exception.PermissionDenied: open('/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/.ipc_lock')
  libtool-2.4.6-r6:  * ERROR: sys-devel/libtool-2.4.6-r6::chromiumos failed (prepare phase):
  libtool-2.4.6-r6:  *   Cannot find the latest automake! Tried 1.16.1:1.16 1.15.1:1.15
  libtool-2.4.6-r6:  * 
  libtool-2.4.6-r6:  * Call stack:
  libtool-2.4.6-r6:  *     ebuild.sh, line  133:  Called src_prepare
  libtool-2.4.6-r6:  *   environment, line 3640:  Called eautoreconf
  libtool-2.4.6-r6:  *   environment, line 1357:  Called _elibtoolize '--auto-ltdl' '--install' '--copy' '--force'
  libtool-2.4.6-r6:  *   environment, line  452:  Called autotools_run_tool 'true' '--install' '--copy' '--force' '--ltdl' '--automake'
  libtool-2.4.6-r6:  *   environment, line  890:  Called autotools_env_setup
  libtool-2.4.6-r6:  *   environment, line  843:  Called die
  libtool-2.4.6-r6:  * The specific snippet of code:
  libtool-2.4.6-r6:  *           [[ ${WANT_AUTOMAKE} == "latest" ]] && die "Cannot find the latest automake! Tried ${_LATEST_AUTOMAKE[*]}";
  libtool-2.4.6-r6:  * 
  libtool-2.4.6-r6:  * If you need support, post the output of `emerge --info '=sys-devel/libtool-2.4.6-r6::chromiumos'`,
  libtool-2.4.6-r6:  * the complete build log and the output of `emerge -pqv '=sys-devel/libtool-2.4.6-r6::chromiumos'`.
  libtool-2.4.6-r6:  * The complete build log is located at '/build/fizz/tmp/portage/logs/sys-devel:libtool-2.4.6-r6:20181002-191817.log'.
  libtool-2.4.6-r6:  * For convenience, a symlink to the build log is located at '/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/temp/build.log'.
  libtool-2.4.6-r6:  * The ebuild environment file is located at '/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/temp/environment'.
  libtool-2.4.6-r6:  * Working directory: '/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/work/libtool-2.4.6/libltdl'
  libtool-2.4.6-r6:  * S: '/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/work/libtool-2.4.6'
  libtool-2.4.6-r6: >>> Failed to emerge sys-devel/libtool-2.4.6-r6 for /build/fizz/, Log file:
  libtool-2.4.6-r6: >>>  '/build/fizz/tmp/portage/logs/sys-devel:libtool-2.4.6-r6:20181002-191817.log'
  libtool-2.4.6-r6: 


 
See also  issue 891527  for the other error in the same build_packages.
Cc: vapier@chromium.org
I don't see any recent related changes. I wonder if it's just a fluke:
portage.exception.PermissionDenied: open('/build/fizz/tmp/portage/sys-devel/libtool-2.4.6-r6/.ipc_lock')

And retrying to emerge it succeeded:
  Retrying emerge of sys-devel/libtool-2.4.6-r6.
  Started sys-devel/libtool-2.4.6-r6 (logged in /tmp/libtool-2.4.6-r6-d5E2CV)
  Completed sys-devel/libtool-2.4.6-r6 (in 0m38.4s)
Components: Infra>Client>ChromeOS>Build OS>Packages
Labels: -Restrict-View-Google
it does look like a flake that shouldn't have happened.  .ipc_lock is an internal path to portage itself ...

Sign in to add a comment