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

[Sylvestre Ledru]

Le 19/07/2016 à 14:09, Santiago Vila a écrit :
> 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.
indeed ;)

>> 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.
because the current test execution is working fine (except for your issue of course).
When a test is failing, I only get what I need and I don't have to dig for the actual error.

>
>> [...] 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?
This is upstream.
Only failing tests are displayed in verbose.
I am not doing any changes for this in llvm of clang (I am (was?) doing it for lldb but this is not your issue here).


Sylvestre