[openssl-project] Fwd: [openssl-commits] FAILED build of OpenSSL branch OpenSSL_1_1_0-stable with options -d --strict-warnings no-dgram

[Matt Caswell]

On 18/01/18 13:40, Richard Levitte wrote:
> Oh, I see what's happening...
> 
> Here's how things are layed out (crontab):
> 
>   2 22  *   *  0-4   (set -x; cd $HOME/run-checker && bash ./run-checker.sh) >> $HOME/run-checker.cron.log 2>&1
>   2 10  *   *  1-5   (set -x; cd $HOME/run-checker-1.1.0 && bash ./run-checker.sh) >> $HOME/run-checker-1.1.0.cron.log 2>&1
> 
> The trouble is this (current listing):
> 
>     openssl at run:~$ ls -ltr ~/run-checker
>     ...
>     -rw-rw-r--  1 openssl openssl  14644664 Jan 17 22:09 default.tar.xz
>     -rw-rw-r--  1 openssl openssl  14632920 Jan 17 22:17 no-afalgeng.tar.xz
>     ...
>     -rw-rw-r--  1 openssl openssl  14637020 Jan 18 13:30 no-tls.tar.xz
>     drwxrwxr-x 12 openssl openssl      4096 Jan 18 13:31 no-ssl3
>     openssl at run:~$ ls -ltr ~/run-checker-1.1.0
>     ...
>     -rw-rw-r--  1 openssl openssl   7599764 Jan 18 10:05 default.tar.xz
>     -rw-rw-r--  1 openssl openssl   7583800 Jan 18 10:10 no-afalgeng.tar.xz
>     ...
>     -rw-rw-r--  1 openssl openssl   7600464 Jan 18 13:33 no-md2.tar.xz
>     drwxrwxr-x 12 openssl openssl      4096 Jan 18 13:34 no-msan
> 
> The last line in each listing (directory) indicates what job is
> currently running (those directories are gzipped at the end of each
> job).
> 
> Unfortunately, there's no barrier between these runs, so when it comes
> to things like network ports, they trample all over each other.  Now,
> TLSProxy uses hard coded ports, you can see how that gets problematic.
> 
> So I think the option is to jail the two run-checkers, and from recent
> reading, I understand that docker can be used for that kind of thing.
> Trouble is, I've never ever played with docker.  I'm willing to
> experiment, but it will probably be done much quicker if someone can
> give me some quick'n'easy instructions.
> 
> We run this on a Ubuntu 16.04 machine, FYI.
> 
> In the mean time, I'm turning off run-checker, as these reports are
> disruptive and not useful at all.

Why not just switch off the 1.1.0 run-checker for now?

Matt

> 
> In message <7953c900-c709-b662-6f29-3d7f96670e6c at openssl.org> on Thu, 18 Jan 2018 11:44:22 +0000, Matt Caswell <matt at openssl.org> said:
> 
> matt> We're still getting lots of spurious failures from TLSProxy in run-checker:
> matt> 
> matt> ../../openssl/test/recipes/70-test_sslcbcpadding.t .... skipped: Unable
> matt> to start up Proxy for tests
> matt> ../../openssl/test/recipes/70-test_sslcertstatus.t .... skipped: Unable
> matt> to start up Proxy for tests
> matt> ../../openssl/test/recipes/70-test_sslextension.t ..... ok
> matt> ../../openssl/test/recipes/70-test_sslmessages.t ...... skipped: Unable
> matt> to start up Proxy for tests
> matt> ../../openssl/test/recipes/70-test_sslrecords.t ....... Dubious, test
> matt> returned 1 (wstat 256, 0x100)
> matt> Failed 1/11 subtests ../../openssl/test/recipes/70-test_sslsessiontick.t
> matt> ... skipped: Unable to start up Proxy for tests
> matt> ../../openssl/test/recipes/70-test_sslskewith0p.t ..... skipped: Unable
> matt> to start up Proxy for tests
> matt> ../../openssl/test/recipes/70-test_sslvertol.t ........ ok
> matt> ../../openssl/test/recipes/70-test_tlsextms.t ......... Dubious, test
> matt> returned 3 (wstat 768, 0x300)
> matt> 
> matt> 
> matt> Grrrr. WTF?
> matt> 
> matt> Matt
> matt> 
> matt> _______________________________________________
> matt> openssl-project mailing list
> matt> openssl-project at openssl.org
> matt> https://mta.openssl.org/mailman/listinfo/openssl-project
> matt> 
> _______________________________________________
> openssl-project mailing list
> openssl-project at openssl.org
> https://mta.openssl.org/mailman/listinfo/openssl-project
>