Automated report: NetBSD-current/i386 build success

2018-09-24 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2018.09.25.03.50.58 kre src/external/public-domain/xz/dist/src/xz/list.c,v 1.2 Log files can be found at:

daily CVS update output

2018-09-24 Thread NetBSD source update
Updating src tree: P src/UPDATING P src/crypto/external/bsd/openssl/lib/libcrypto/man.inc P src/crypto/external/bsd/openssl/lib/libcrypto/arch/aarch64/crypto.inc P src/crypto/external/bsd/openssl/lib/libcrypto/arch/alpha/crypto.inc P

Automated report: NetBSD-current/i386 build failure

2018-09-24 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2018.09.24.22.36.03. An extract from the build.sh output follows:

Cannot build evbarm-current with Clang

2018-09-24 Thread Adam
Greetings, My current build of evbarm (MACHINE_ARCH=earmv7hf) fails with: [...] 'arm7m' is not a recognized processor for this target (ignoring processor) [...] /dist/src/sys/arch/acorn32/stand/lib/riscoscalls.S:360:2: warning: use of SP or PC in the list is deprecated stmfd sp!, {r4, fp, ip,

"Montonic clock has gone backwards" on amd64 current (GENERIC) running as VBox guest

2018-09-24 Thread Rares Aioanei
Hey, I know that this has been reported before (https://mail-index.netbsd.org/netbsd-users/2017/12/23/msg020349.html) and I know about Maya's PR for Xen (52664), but I still see it. Here are the outputs of the sysctl settings as requested by Christos in the aforementioned thread : 1. sysctl -a |

Automated report: NetBSD-current/i386 test failure

2018-09-24 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: crypto/libcrypto/t_hashes:md4 crypto/libcrypto/t_hashes:md5 crypto/libcrypto/t_hashes:ripemd crypto/libcrypto/t_libcrypto:rand The above tests failed in each of