From d27e0bff5ac7ea8aae81fb00e362e3a63b47b8f0 Mon Sep 17 00:00:00 2001 From: Todd Gamblin Date: Wed, 25 Aug 2021 08:39:00 -0700 Subject: installation: filter padding from binary installs, too (#25600) #25303 filtered padding from build output, but it's still there in binary install/relocate output, so our CI logs are still quite long and frequently hit the limit. - [x] add context handler from #25303 to buildcache installation as well --- lib/spack/spack/installer.py | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/lib/spack/spack/installer.py b/lib/spack/spack/installer.py index dc0180feed..8ae2fd410d 100644 --- a/lib/spack/spack/installer.py +++ b/lib/spack/spack/installer.py @@ -367,8 +367,13 @@ def _process_binary_cache_tarball(pkg, binary_spec, explicit, unsigned, pkg_id = package_id(pkg) tty.msg('Extracting {0} from binary cache'.format(pkg_id)) - binary_distribution.extract_tarball(binary_spec, tarball, allow_root=False, - unsigned=unsigned, force=False) + + # don't print long padded paths while extracting/relocating binaries + with spack.util.path.filter_padding(): + binary_distribution.extract_tarball( + binary_spec, tarball, allow_root=False, unsigned=unsigned, force=False + ) + pkg.installed_from_binary_cache = True spack.store.db.add(pkg.spec, spack.store.layout, explicit=explicit) return True -- cgit v1.2.3-60-g2f50