-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log files in robot build leak into each other #3533
Comments
Building on Ubuntu 16.04 with Python 2.7.12, I get less mention of other builds in my logs, mostly limited to the X11 bundle, but it still seems a bit fishy:
|
This is indeed easily triggered by something that uses Bundle easyblock. |
EB 4.3.2 has the problem, so it's not a new thing |
I built with
eb R-4.0.0-foss-2020a.eb -r
on Ubuntu 20.04, Python 3.8.5, framework 5d8747a and ran out of disk space to many gigabytes of logs.Investigation shows that there are multiple log files in the uniquely-named directory in /tmp; each individual log file like
easybuild-Xvfb-1.20.9-20201221.170919.PHYQe.log
andeasybuild-xauth-1.1-20201221.170914.UrvMk.log
contains the output of many other builds in that session, including full build output from libraries later in the build sequence.For example, the Xvfb log, being rather early in the dependency chain, contains the following entries spread out across the file:
The transitions in that log file claim to be closing the log for various applications and carries on logging nevertheless:
The full log set obtained from the uniquely-named directory in /tmp can be found at https://zao.se/~zao/eb/R-huge-logs.tar.zst (844 MiB compressed!) expanding to 42.7 GiB.
Two individual log files and the overall build log:
Notable here is that the lingering logs seem to be either Bundle configs or bundled in such a config.
Log file names:
The text was updated successfully, but these errors were encountered: