Bug#819278: llvm-toolchain-3.8: Build not reliable

[Santiago Vila]

On Tue, 19 Jul 2016, Sylvestre Ledru wrote:

> Le 19/07/2016 à 10:32, Santiago Vila a écrit :
> > On Tue, 19 Jul 2016, Sylvestre Ledru wrote:
> > 
> > > The four are caused by the same issue: a test freezes.
> > > Having the name of the test would be super helpful so that we can report
> > > a bug upstream to fix it.
> > 
> > I fully agree, and I'd love to provide the test which fails, but the
> > build process is completely silent about the tests.
>
> Looking at the list of processes should be enough.

Maybe, but for that to happen I have to be "present" during the build,
so to speak, and the build takes at least five hours in the fastest machine
I had. Looking at a build log in real time is not a very entertaining
TV program.

It would be much better if the build process printed something on
stdout during the tests.

> Here, we should not list all the tests (too many of them). [...]

Hmm. Why not? The building of a package should not be a black box.

That would be the natural thing. Small packages have small build logs.
Large packages have large build logs. Packages that are not very large
but have a lot of tests have large build logs as well.

We take that for granted and accept it as a normal thing. It's not a
problem.

But even if a large build log is a problem at all, we have a bigger problem
as a result, which is that we don't know what's happening at all.

> [...] I am happy to apply any patch to help you in your goals.

Fine, but you know the code a lot better than me, so I hope you don't
mind if I ask some simple questions.

For example: I look at debian/rules and I don't see anything which
deliberately disables build log verbosity.

Is this lack of verbosity in the test suite a Debian change or is it
an upstream thing?

Thanks.