On 02/11/14 21:33, Ximin Luo wrote: > On 01/11/14 18:41, Holger Levsen wrote: >> >> well, you are the maintainer you can make it output the test.log if there >> are >> failures... >> > > It's pretty tricky to do this and I don't want to commit a hack that bypasses > automake. I've filed a feature request upstream to automake: > http://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=automake Hopefully it will show > up soon, I called in "feature: output test failures to stdout". >
OK, so it turns out you can do this in automake easily with a flag. I've added it to debian/rules. > OTOH ideally, the CI system would let me view these test logs as well. It's a > bit unhelpful to give partial information when there's a problem. I didn't > choose to use these systems, and there is no Debian policy that states > "packages should output test logs to stdout"; whoever set these systems up > should be working to make sure it's as useful for as many packages as > possible. Apparently there is a way to get jenkins to keep artefacts: > > http://stackoverflow.com/questions/9280619/how-can-i-configure-jenkins-to-show-my-logs-in-the-workspace > > The pattern suggested, **/*.log seems pretty reasonable and should cover most > test logs, without picking up large build products like object files etc. > >> >> it's in ./facilitator/test-suite.log and attached. >> >> :) >> >> I'd be happy to rebuild again if you can give me something to try :) >> > > Thanks, that was very useful. I think I have a fix - try this? > > https://gitweb.torproject.org/debian/flashproxy.git/commitdiff/fedcd28195f03fdc9bb456b7e16d9c14b3648478 > Candidate for 1.7-2: https://mentors.debian.net/package/flashproxy Let me know if it works, and I'll upload a proper release. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
signature.asc
Description: OpenPGP digital signature
