This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/librumphijack/t_vfs:ln_nox
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The following commits were made
Updating src tree:
P src/bin/ln/ln.c
P src/distrib/sets/mkvars.mk
P src/doc/3RDPARTY
P src/external/bsd/pkg_install/sbin/Makefile.inc
P src/lib/libc/sys/_lwp_create.2
P src/lib/libedit/filecomplete.c
P src/lib/libedit/filecomplete.h
P src/lib/libedit/readline.c
P src/sbin/fsck_ext2fs/pass1.c
P src
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 2017.04.21.23.49.17.
An extract from the build.sh output follows:
unzip.c:(.text.startup+0xb14): undefined reference
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2017.04.21.22.15.44 sjg src/usr.bin/make/str.c,v 1.38
2017.04.21.22.15.44 sjg src/usr.bin/make/unit-tests/modmatch.exp,v 1.3
2017.04.21.22.15.44 sjg
On Friday 21 Apr 2017, at 22:15, Mindaugas Rasiukevicius wrote:
| > #11 0x804b3075 in panic (
| > fmt=fmt@entry=0x806b6790 "uvm_km_check_empty: va %p
| > has pa 0x%llx") at /usr/src/sys/kern/subr_prf.c:258
| > #12 0x8044ed05 in uvm_km_check_empty (
| > map=map@en
Hello,
On Fri, 21 Apr 2017 16:34:33 +
co...@sdf.org wrote:
> Hi,
>
> mprotect (and ASLR) are security measures that not all pkgsrc packages
> can survive, so some packages had NOT_PAX_MPROTECT_SAFE set for some
> binaries, to disable it.
>
> However the condition for using NOT_PAX_MPROTECT_
Anthony Mallet | Trying to upgrade from 7.99.44 to today's -current, I have a panic
> | right away when starting npf. The boot with npf disabled is fine (see
> | note below), then when manually running `npfctl reload` the machine
> | reboots right aways with absolutely no diagnostic. This is an is
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 2017.04.21.19.18.05.
An extract from the build.sh output follows:
/tmp/bracket/build/2017.04.21.19.18.05-i386/tools
Hi,
as part of work on jdolecek-ncq branch, I've made some mechanical
changes to adjust the umass_isdata.c driver code to still hopefully
work. I don't have the hardware though, so I'd like to have a real
confirmation from somebody who does, before the branch would be
merged.
If you have the hard
Hi,
mprotect (and ASLR) are security measures that not all pkgsrc packages
can survive, so some packages had NOT_PAX_MPROTECT_SAFE set for some
binaries, to disable it.
However the condition for using NOT_PAX_MPROTECT_SAFE was incorrectly
only done for NetBSD/amd64.
The outcome should've been th
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2017.04.21.11.49.31 kre src/sys/dev/pci/pci_subr.c,v 1.178
Log files can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2017.04.html#201
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 2017.04.21.09.01.52.
An extract from the build.sh output follows:
--- pci_subr.pico ---
/tmp/bracket/build/2017
12 matches
Mail list logo
