On Tue, 08/09 18:11, Daniel P. Berrange wrote: > > Can we get this report to include details of the > > a) the software versions of gcc, binutils, and any -devel packages > we're building against > > b) the exact arguments + env variables used to invoke configure, > not merely its output > > so we don't have to go digging into the docker test systemm to > try and reverse engineer this info
The whole point of docker test system is offer a relatively easy reproducer to developers, so I'm reluctant to engineer patchew or the test script it runs for that. On the other hand, it's reasonable to allow the docker testing code to be more verbose than currently. Or maybe we can patch ./configure to output these information? Fam
