Daniel P. Berrangé writes:
> When configure fails in CI systems we must be able to see the contents
> of the config.log file to diagnose the root cause.
>
> Signed-off-by: Daniel P. Berrangé
queued thanks.
--
Alex Bennée
On 06/12/2018 09:15 AM, Eric Blake wrote:
> On 06/12/2018 03:28 AM, Daniel P. Berrangé wrote:
>> When configure fails in CI systems we must be able to see the contents
>> of the config.log file to diagnose the root cause.
>>
>> Signed-off-by: Daniel P. Berrangé
>> ---
>> .travis.yml | 4 ++--
>>
On 06/12/2018 03:28 AM, Daniel P. Berrangé wrote:
When configure fails in CI systems we must be able to see the contents
of the config.log file to diagnose the root cause.
Signed-off-by: Daniel P. Berrangé
---
.travis.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, 06/12 09:28, Daniel P. Berrangé wrote:
> When configure fails in CI systems we must be able to see the contents
> of the config.log file to diagnose the root cause.
>
> Signed-off-by: Daniel P. Berrangé
> ---
> .travis.yml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
When configure fails in CI systems we must be able to see the contents
of the config.log file to diagnose the root cause.
Signed-off-by: Daniel P. Berrangé
---
.travis.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index
