Automated report: NetBSD-current/i386 build failure

2018-02-08 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.02.09.04.38.24. An extract from the build.sh output follows: /tmp/bracket/build/2018.02.09.04.38.24-i386/destdi

Automated report: NetBSD-current/i386 build success

2018-02-08 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.02.09.03.20.21 christos src/tests/crypto/libcrypto/threads/Makefile,v 1.5 2018.02.09.03.53.07 ozaki-r src/tests/net/net/t_ping_opts.sh,v 1.3 Log f

Install Current - Hostname not set

2018-02-08 Thread Ron Georgia
All, Just an FYI. I’ve installed Netbsd-8 on two different machines and one VM and in all cases the hostname did not make into the rc.conf file. -- Ron Georgia “Fail fast, fail often.”

Automated report: NetBSD-current/i386 build failure

2018-02-08 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.02.08.21.59.11. An extract from the build.sh output follows: rm -f .gdbinit echo "set solib-absolute-prefix

Automated report: NetBSD-current/i386 build success

2018-02-08 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. Between the last failed build and the successful build, a total of 1032 revisions were committed, by the following developers: christos jakllsch maxv Log files can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2018.