On Thu, Dec 26, 2019 at 02:37:03AM +0000, Daniel Shahaf wrote: > Nathan Hartman wrote on Wed, Dec 25, 2019 at 12:07:35 -0500: > > On Wed, Dec 25, 2019 at 1:38 AM Yasuhito FUTATSUKI <futat...@poem.co.jp> > > wrote: > > > > > > On 2019/12/25 6:38, Nathan Hartman wrote: > > > > When running the regression test suite via the 'svn-check' target of > > > > tools/dev/unix-build/Makefile.svn, is there a convenient way to see a > > > > "All tests successful"-type summary at the very end? > > > > > > > > That is to say, is there a better way than what I'm doing now, > > > > which is: > > > > > > > > $ cat tests.log.* | grep ^FAIL > > > > > > It isn't an answer for your question, but this can miss 'XPASS'. > > > > Thank you. Yes, you are right. > > > > I ran it again, redirecting stderr and stdout to a file, and that > > generates much less output (around 2000 lines). But if someone has a > > better way, I'd love to hear about it. > > For starters, you can use the fails.log files. They're generated by > build/run_tests.py after tests.log gets fully written (not during the run), > and > they aren't removed when a test run starts (so beware of them remaining around > after you've already fixed a bug), but if they exist at all, they contain only > FAILs and XPASSes. If you're just looking for a quick "Did any test fail?" > bit, you can just check whether any fails.log.* file exists.
Yes that is exactly what I do: Look for fails.log.* > I don't know of an easy answer to your question for bindings tests. Does the > svn-check target exit non-zero when any test has failed? If it did, that > would > at least handle the common case of "All tests passed". > > stsp may know more. Check the svn-bb-openbsd buildbot scrips and you will find the answer :) (It greps the binding test log files.) > > To make successfully on Debian Buster, because of OpenSSL 1.1.1d, I > > modified Makefile.svn to use Serf 1.4.x (from branches as there is no > > 1.4.x release yet) and Cyrus SASL 2.1.27. Also I removed all the > > serf-old targets which are applicable to svn 1.5 and were breaking the > > build for me, thanks again to OpenSSL. I didn't commit my changes > > because that will probably break the OpenBSD buildbot. > > It would be nice to find a way for you to share your changes without breaking > the bot. Could you talk to stsp about this? Yes I can help here. Please share your patches and I will integrate them. I kept serf-old around to be able to build 1.5 but at this point it's fine for me to lose the ability to build it.
