On 2019-12-15 20:09, Edgar Pettijohn wrote:
On 2019-12-15 18:18, Edgar Pettijohn wrote:
laptop$ uname -a
NetBSD laptop.my.domain 9.99.24 NetBSD 9.99.24 (GENERIC_KASLR) #0:
Sat Dec 14 21:37:06 CST 2019
r...@laptop.my.domain:/usr/obj/sys/arch/amd64/compile/GENERIC_KASLR
amd64
Testing ssl
On 2019-12-15 18:18, Edgar Pettijohn wrote:
laptop$ uname -a
NetBSD laptop.my.domain 9.99.24 NetBSD 9.99.24 (GENERIC_KASLR) #0: Sat
Dec 14 21:37:06 CST 2019
r...@laptop.my.domain:/usr/obj/sys/arch/amd64/compile/GENERIC_KASLR amd64
Testing ssl with httpd run from inetd I get the following
The NetBSD-current/i386 build is working again.
Between the last failed build and the successful build, a total of
2356 revisions were committed, by the following developers:
ad
christos
uwe
Log files can be found at:
laptop$ uname -a
NetBSD laptop.my.domain 9.99.24 NetBSD 9.99.24 (GENERIC_KASLR) #0: Sat
Dec 14 21:37:06 CST 2019
r...@laptop.my.domain:/usr/obj/sys/arch/amd64/compile/GENERIC_KASLR amd64
Testing ssl with httpd run from inetd I get the following in the xferlog:
laptop$ sudo tail -n 20
On Sun, Dec 15, 2019 at 10:10:15PM +, NetBSD Test Fixture wrote:
> This is an automatically generated notice of a NetBSD-current/i386
> build failure.
Fixed already with rev 1.285 src/sys/sys/vnode.h.
Andrew
> The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
> using
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 2019.12.15.20.33.22.
An extract from the build.sh output follows:
On Sun, 15 Dec 2019 at 19:10, Bodie wrote:
>
>
>
> On 12.12.2019 17:38, Maxime Villard wrote:
> > Le 12/12/2019 à 16:34, Valery Ushakov a écrit :
> >> On Thu, Dec 12, 2019 at 06:47:50 +0100, Bodie wrote:
> >>
> >>> On 11.12.2019 23:32, Valery Ushakov wrote:
> On Wed, Dec 11, 2019 at 23:15:38
On 12.12.2019 17:38, Maxime Villard wrote:
Le 12/12/2019 à 16:34, Valery Ushakov a écrit :
On Thu, Dec 12, 2019 at 06:47:50 +0100, Bodie wrote:
On 11.12.2019 23:32, Valery Ushakov wrote:
On Wed, Dec 11, 2019 at 23:15:38 +0100, Bodie wrote:
FYI https://www.virtualbox.org/ticket/19146
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.12.15.16.00.54 christos src/external/bsd/nsd/dist/.travis.yml,v 1.1
2019.12.15.16.00.54 christos src/external/bsd/nsd/dist/README.md,v 1.1
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 2019.12.15.15.28.43.
An extract from the build.sh output follows:
^
In file
OK, looks like this is fixed. With the fix I just committed, these
tests now pass:
# cd /usr/tests/dev/sysmon
# atf-run t_swsensor | atf-report
Tests root: /usr/tests/dev/sysmon
t_swsensor (1/1): 5 test cases
alarm_sensor: [57.065200s] Passed.
entropy_interrupt_sensor: [36.167103s]
Hi,
Since 9.99.18 I am not able to build lsof; I get:
...
gcc -O2 -DNETBSDV=700 -DN_UNIXV=/dev/ksyms -DHASKVMGETPROC2
-DHASNFSPROTO -DHASIPv6 -DHASFDESCFS=1 -DHASFDLINK -DHASNULLFS
-DHASPROCFS -DHASPROCFS_PFSROOT -DHASBUFQ_H -DHAS9660FS=1
-DHASMSDOSFS=1 -DHASKERNFS -DHASKERNFS_KFS_KT
Working on it. As far as I can tell, it just needs to initialize the
newly-created module_hook synchronization variables.
I'll commit the fix as soon as I can test it.
Index: rump.c
===
RCS file:
The following test cases are now failing on multiple testbeds:
dev/sysmon/t_swsensor/alarm_sensor
dev/sysmon/t_swsensor/entropy_interrupt_sensor
dev/sysmon/t_swsensor/entropy_polled_sensor
dev/sysmon/t_swsensor/limit_sensor
dev/sysmon/t_swsensor/simple_sensor
14 matches
Mail list logo
