diff options
| author | Todd Gamblin <gamblin2@llnl.gov> | 2021-07-12 14:48:52 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-12 21:48:52 +0000 |
| commit | f58b2e03ca5611a92f559f4b81eeae883c7b274a (patch) | |
| tree | 705133de6ab2cef44f59fc7cc0689ced103c01a8 /etc | |
| parent | 34b763f792aa3fecd321a62eb103a803d954718a (diff) | |
| download | spack-f58b2e03ca5611a92f559f4b81eeae883c7b274a.tar.gz spack-f58b2e03ca5611a92f559f4b81eeae883c7b274a.tar.bz2 spack-f58b2e03ca5611a92f559f4b81eeae883c7b274a.tar.xz spack-f58b2e03ca5611a92f559f4b81eeae883c7b274a.zip | |
build output: filter padding out of console output when `padded_length` is used (#24514)
Spack allows users to set `padded_length` to pad out the installation path in
build farms so that any binaries created are more easily relocatable. The issue
with this is that the padding dominates installation output and makes it
difficult to see what is going on. The padding also causes logs to easily
exceed size limits for things like GitLab artifacts.
This PR fixes this by adding a filter in the logger daemon. If you use a
setting like this:
config:
install_tree:
padded_length: 512
Then lines like this in the output:
==> [2021-06-23-15:59:05.020387] './configure' '--prefix=/Users/gamblin2/padding-log-test/opt/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_placeholder__/__spack_path_pla/darwin-bigsur-skylake/apple-clang-12.0.5/zlib-1.2.11-74mwnxgn6nujehpyyalhwizwojwn5zga
will be replaced with the much more readable:
==> [2021-06-23-15:59:05.020387] './configure' '--prefix=/Users/gamblin2/padding-log-test/opt/[padded-to-512-chars]/darwin-bigsur-skylake/apple-clang-12.0.5/zlib-1.2.11-74mwnxgn6nujehpyyalhwizwojwn5zga
You can see that the padding has been replaced with `[padded-to-512-chars]` to
indicate the total number of characters in the padded prefix. Over a long log
file, this should save a lot of space and allow us to see error messages in
GitHub/GitLab log output.
The *actual* build logs still have full paths in them. Also lines that are
output by Spack and not by a package build are not filtered and will still
display the fully padded path. There aren't that many of these, so the change
should still help reduce file size and readability quite a bit.
Diffstat (limited to 'etc')
0 files changed, 0 insertions, 0 deletions