New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 778450 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jan 2018
Cc:
█ warx@chromium.org
teravest@chromium.org
█ justincarlson@chromium.org
dgarr...@chromium.org
semenzato@chromium.org
█ josa...@chromium.org
malaykeshav@chromium.org
pprabhu@chromium.org
jdufault@chromium.org
jbudorick@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

CreateTarball fails during DebugSymbols stage for 63 release bot lakitu-release

Project Member Reported by jdufault@chromium.org, Oct 25 2017 
This has happened a few times on lakitu-release, ie, [1] and [2].

The DebugSymbols stage fails because CreateTarball fails twice in a row

  22:21:50: WARNING: CreateTarball: tar: source modification time changed (see crbug.com/547055), retrying once

This looks like a continuation of issue 547055.

1: https://uberchromegw.corp.google.com/i/chromeos_release/builders/lakitu-release%20release-R63-10032.B
2: https://uberchromegw.corp.google.com/i/chromeos_release/builders/lakitu-release%20release-R63-10032.B/builds/4

Comment 1 by pprabhu@chromium.org, Oct 25 2017 

This is https://bugs.chromium.org/p/chromium/issues/detail?id=547055 resurrected.

See the error message:
22:21:40: INFO: RunCommand: sudo -n 'CROS_CACHEDIR=/b/c/cbuild/repository/.cache' 'CROS_SUDO_KEEP_ALIVE=unknown' -- tar --exclude debug/usr/local/build/autotest --exclude debug/tests --sparse -I /usr/bin/pigz -cf /b/c/cbuild/repository/buildbot_archive/lakitu-release/R63-10032.5.0/debug.tgz debug in /b/c/cbuild/repository/chroot/build/lakitu/usr/lib
tar: debug/usr/lib64: file changed as we read it
22:21:50: WARNING: CreateTarball: tar: source modification time changed (see crbug.com/547055), retrying once[0
22:21:50: INFO: RunCommand: sudo -n 'CROS_CACHEDIR=/b/c/cbuild/repository/.cache' 'CROS_SUDO_KEEP_ALIVE=unknown' -- tar --exclude debug/usr/local/build/autotest --exclude debug/tests --sparse -I /usr/bin/pigz -cf /b/c/cbuild/repository/buildbot_archive/lakitu-release/R63-10032.5.0/debug.tgz debug in /b/c/cbuild/repository/chroot/build/lakitu/usr/lib
tar: debug/usr/bin: file changed as we read it

Comment 2 by pprabhu@chromium.org, Oct 25 2017 

DebugSymobls runs in parallel with a lot of stages. It could be any one of them (http://shortn/_gUHFv0IAay) mucking with the files being tarred.

Comment 3 by dgarr...@chromium.org, Oct 26 2017 

Maybe we could fix this by moving the location that holds the symbols so something specific to this stage?

Comment 4 by teravest@chromium.org, Oct 30 2017

Cc: teravest@chromium.org justincarlson@chromium.org
FYI this is still happening:
https://luci-milo.appspot.com/buildbot/chromeos/lakitu-release/2793

Comment 5 by jdufault@chromium.org, Oct 30 2017

Cc: malaykeshav@chromium.org warx@chromium.org

Comment 6 by dgarr...@chromium.org, Oct 30 2017 

This has been cropping back up all over the place.

Comment 7 by akes...@chromium.org, Jan 8 2018

Mergedinto: 789058
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment