[Libre-soc-dev] Build failed: Kazan / mirrors / openpower-isa master: Commit 2f3b080: add version constraints on setup install_requires

[Jacob Lifshay]

On Tue, Jun 14, 2022 at 8:17 PM Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:
>
> On Wed, Jun 15, 2022 at 1:17 AM Jacob Lifshay via Libre-soc-dev
> <libre-soc-dev at lists.libre-soc.org> wrote:
>
> > >  [33;1mJob's log exceeded limit of 4194304 bytes.
> > > Job execution will continue but no more output will be collected. [0;m
> > >
> >
> > Luke, that's why I keep saying you need less print() calls...
>
> corollary: that is why i have told you that *in no way* would it be
> practical or acceptable to have the CI build output sent to a mailing
> list stored and archived on the server: the server would be
> completely overwhelmed within a few months.

The problem isn't storing the build log, the problem is that gitlab ci
truncates the output, making ci not show which tests fail because that
info comes later than 4M into the build log.

du -h /home/build/gitlab-ci-archiver/build-archive.git/
...
34M /home/build/gitlab-ci-archiver/build-archive.git/

That's from 417 builds. We have enough space that we could reasonably
use 10GB for the git repo, which would be approximately 120k builds at
that rate...

*28 years* worth of 2hr builds. with 28 years of storage, we have no
storage problems (my computer will be replaced before then).
>
> that debug output log is absolutely critical and essential for the
> development of the simulator.  it is actually an extremely complex
> piece of software that would be absolutely impossible to have
> developed without having full, complete and detailed log output.
>
> when doing further development that debug log output will INCREASE.
>
> in absolutely no way whatsoever will that debug log output be
> removed or decrease, it is far too important.

Then at least switch to using python logging, where you can select how
verbose you want it to be, redirect it to a file and/or filter it.

Jacob