[CRIU] [PATCH 5/5] pie: piegen -- Enable printing debug info during build

[Laurent Dufour]

On 09/06/2015 17:03, Cyrill Gorcunov wrote:
> On Tue, Jun 09, 2015 at 04:55:28PM +0200, Laurent Dufour wrote:
>>>>
>>>> This generates a lot of output and I think that only CRIU developpers
>>>> would be interested in the detailed.
>>>> I guess we may send the output in a log file. See patch attached.
>>>
>>> No no. Yes it's suitable for developers mostly but if we move it to
>>> the file I fear it won't be able to fetch output from automatisation
>>> services like Travis. Let live with a bunch of debug info at least for
>>> month or something.
>>
>> Well, I had to do this when I was debugging the ppc relocation.
>>
>> Since I'm building with 15 CPUs (and this is a small VM ;) ), I got all
>> the outputs interleaved, including parasite/restorer blob's relocations.
>> For the other output, this doesn't matter but piegen is very verbose,
>> and interleave is quite to happen. Thus the piegen's outputs are
>> unusable and I had to either build using only 1 CPU or put the output in
>> a file like this...
>>
>> This being said, I don't use/know Travis... ;)
> 
> Ideally would be cool if we print this output for
> 
> 	make V=1 only
> 
> so please wait some time until I add such ability (or I would
> be more happy if someone cook one for me ;)
> 

What about sending the ouput to a file except when V=1 then the output
is sent to the standard output. But again when building with multiple
CPUs the output is interleaved and not really usable.

For my information, what is the issue with Travis ?