Fixed in:
src/tests/lib/libc/sys/t_ptrace_wait.c r.1.141
src/tests/lib/libc/sys/t_ptrace_wait.h r.1.18
On 12.11.2019 18:34, Paul Goyette wrote:
> I've confirmed that these failures occur with builds from before
> my most recent changes. So, as Kamil indicated (and Joerg on
> IRC), it ain't my
I've confirmed that these failures occur with builds from before
my most recent changes. So, as Kamil indicated (and Joerg on
IRC), it ain't my fault!
On Tue, 12 Nov 2019, Paul Goyette wrote:
Hmmm, this might be my fault. Checking/bisecting now...
On Tue, 12 Nov 2019, NetBSD Test Fixture
The problem is in ATF tests with assumptions that are no longer valid.
We are working on this. The right fix is to improve the tests.
On 12.11.2019 13:53, Paul Goyette wrote:
> Hmmm, this might be my fault. Checking/bisecting now...
>
> On Tue, 12 Nov 2019, NetBSD Test Fixture wrote:
>
>>
On Tue, 12 Nov 2019, Kamil Rytarowski wrote:
The problem is in ATF tests with assumptions that are no longer valid.
We are working on this. The right fix is to improve the tests.
Oh, good - not my fault after all!
Thanks!
On 12.11.2019 13:53, Paul Goyette wrote:
Hmmm, this might be
Hmmm, this might be my fault. Checking/bisecting now...
On Tue, 12 Nov 2019, NetBSD Test Fixture wrote:
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libc/sys/t_ptrace_wait3:thread_concurrent_signals
On 12.11.2019 09:26, NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> lib/libc/sys/t_ptrace_wait3:thread_concurrent_signals
>
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libc/sys/t_ptrace_wait3:thread_concurrent_signals
lib/libc/sys/t_ptrace_wait3:trace_thread_lwpcreate_and_exit
Sorry, I misread the logs - it was the wait4 variant of the test that
succeeded in the test run after the wait6 one failed.
In any case, this simply looks like flaky/racy tests, or ptrace(),
(and certainly unrelated to the listed commits).
kre
Date:Fri, 18 Oct 2019 15:14:04 + (UTC)
From:NetBSD Test Fixture
Message-ID: <157141164388.24477.1554860029123...@babylon5.netbsd.org>
| The newly failing test case is:
|
| lib/libc/sys/t_ptrace_waitid:tracer_sysctl_lookup_without_duplicates
While
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/sys/t_ptrace_waitid:tracer_sysctl_lookup_without_duplicates
The above test failed in each of the last 3 test runs, and passed in
at least 21 consecutive runs before
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/arp/t_arp:arp_purge_on_route_change
net/ndp/t_ndp:ndp_purge_on_route_change
The above tests failed in each of the last 3 test runs, and passed in
at least 27
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
fs/vfs/t_vfsops:p2k_ffs_tstatvfs
fs/vfs/t_vfsops:puffs_tstatvfs
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before
On 21.09.2019 18:18, Robert Elz wrote:
> Date:Sat, 21 Sep 2019 15:40:49 + (UTC)
> From:NetBSD Test Fixture
> Message-ID: <156908044959.2857.11788397410553967...@babylon5.netbsd.org>
>
> | The newly failing test cases are:
> |
> |
Date:Sat, 21 Sep 2019 15:40:49 + (UTC)
From:NetBSD Test Fixture
Message-ID: <156908044959.2857.11788397410553967...@babylon5.netbsd.org>
| The newly failing test cases are:
|
| fs/vfs/t_ro:ext2fs_attrs
| fs/vfs/t_ro:ffs_attrs
|
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
fs/vfs/t_ro:ext2fs_attrs
fs/vfs/t_ro:ffs_attrs
fs/vfs/t_ro:ffslog_attrs
fs/vfs/t_ro:msdosfs_attrs
fs/vfs/t_ro:nfs_attrs
fs/vfs/t_ro:nfsro_attrs
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/gen/execve/t_execve:t_execve_null
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The following
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/arp/t_arp:arp_rtm
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 between
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/ndp/t_ndp:ndp_rtm
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 between
On Mon, Aug 26, 2019 at 03:13:29AM +, NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> net/if_ipsec/t_ipsec_pfil:ipsecif_pfil_esp_null
>
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/if_ipsec/t_ipsec_pfil:ipsecif_pfil_esp_null
net/if_ipsec/t_ipsec_pfil:ipsecif_pfil_esp_rijndaelcbc
net/npf/t_npf:npf_bpf
net/npf/t_npf:npf_conn
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libpthread/t_condwait:cond_wait_mono
lib/libpthread/t_condwait:cond_wait_real
The above tests failed in each of the last 3 test runs, and passed in
at least 27
On Thu, 8 Aug 2019, Paul Goyette wrote:
I am investigating...
This should be fixed by sys/kern/kern_module.c rev 1.138
On Thu, 8 Aug 2019, NetBSD Test Fixture wrote:
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
I am investigating...
On Thu, 8 Aug 2019, NetBSD Test Fixture wrote:
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
modules/t_builtin:busydisable
The above test failed in each of the last 3 test runs, and passed in
at
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
modules/t_builtin:busydisable
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
The NetBSD Test Fixture wrote:
> This is an automatically generated notice of a new failure of the
> NetBSD test suite.
>
> The newly failing test case is:
>
> lib/libc/sys/t_ptrace_waitpid:tracer_sysctl_lookup_without_duplicates
>
> The above test failed in each of the last 3 test runs,
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/sys/t_ptrace_waitpid:tracer_sysctl_lookup_without_duplicates
The above test failed in each of the last 3 test runs, and passed in
at least 22 consecutive runs before
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/if_ipsec/t_ipsec_natt:ipsecif_natt_transport_rijndaelcbc
The above test failed in each of the last 5 test runs, and passed in
at least 23 consecutive runs before that.
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/if_ipsec/t_ipsec_natt:ipsecif_natt_transport_null
net/ipsec/t_ipsec_natt:ipsec_natt_transport_ipv4_null
net/npf/t_npf:npf_rule
net/npf/t_npf:npf_table
The
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/npf/t_npf:npf_nat
The above test failed in each of the last 5 test runs, and passed in
at least 22 consecutive runs before that.
The following commits were made between
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/ndp/t_ndp:ndp_cache_state
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
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
ipf/t_filter_exec:f13
ipf/t_filter_exec:f24
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The
On 21.06.2019 18:09, NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> fs/vfs/t_vnops:ext2fs_rename_dir
> fs/vfs/t_vnops:ext2fs_rename_reg_nodir
> fs/vfs/t_vnops:ffs_rename_dir
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
fs/vfs/t_vnops:ext2fs_rename_dir
fs/vfs/t_vnops:ext2fs_rename_reg_nodir
fs/vfs/t_vnops:ffs_rename_dir
fs/vfs/t_vnops:ffs_rename_reg_nodir
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libcurses/t_curses:copywin
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
On 03.05.2019 11:20, NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> lib/libc/sys/t_ptrace_wait3:bytes_transfer_alignment_piod_read_auxv
>
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libc/sys/t_ptrace_wait3:bytes_transfer_alignment_piod_read_auxv
lib/libc/sys/t_ptrace_wait4:bytes_transfer_alignment_piod_read_auxv
On 02.05.2019 01:54, NetBSD Test Fixture wrote:
> This is an automatically generated notice of a new failure of the
> NetBSD test suite.
>
> The newly failing test case is:
>
> usr.bin/gdb/t_regress:pie
>
Addressed in sys_ptrace_common.c 1.5
It looks like a bug in GDB, but for now I will
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
usr.bin/gdb/t_regress:pie
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
Date:Tue, 30 Apr 2019 21:58:19 + (UTC)
From:NetBSD Test Fixture
Message-ID: <155666149938.7910.2797000443449332...@babylon5.netbsd.org>
| The newly failing test cases are:
|
| sys/net/t_print:dl_print
| sys/net/t_print:sdl_print
These should be
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
sys/net/t_print:dl_print
sys/net/t_print:sdl_print
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The
Date:Mon, 29 Apr 2019 12:02:10 +0300
From:Valery Ushakov
Message-ID: <20190429090210.gd11...@pony.stderr.spb.ru>
| E.g. in sys/arch/sh3/include/adcreg.h
Yes, I noticed many uses in arch/* ... I sampled a bunch of them,
and was mostly finding "old" style uses... So
On Mon, Apr 29, 2019 at 10:29:43 +0700, Robert Elz wrote:
> I've done some searching (not exhaustive for sure) and the only
> thing I can find that uses 'F' in our tree that I can find is
> (which provided the newly added example in snprintb.3)
> which is missing that final NUL after the F field
Thanks!
christos
> On Apr 28, 2019, at 10:33 PM, Robert Elz wrote:
>
>Date:Mon, 29 Apr 2019 08:58:43 +0700
>From:Robert Elz
>Message-ID: <17972.1556503...@jinx.noi.kre.to>
>
> | I know what is happening with that, and I will fix...
> |
> | The problem relates
Date:Mon, 29 Apr 2019 09:33:59 +0700
From:Robert Elz
Message-ID: <22739.1556505...@jinx.noi.kre.to>
| Upon reflection, I'm inclined to instead [...]
And upon further reflection, and noticing this sentence in
the snprintb() man page (snprintb.3)
Finally,
Date:Mon, 29 Apr 2019 08:58:43 +0700
From:Robert Elz
Message-ID: <17972.1556503...@jinx.noi.kre.to>
| I know what is happening with that, and I will fix...
|
| The problem relates to a difference of opinion/misunderstanding
| of the 'F' (new style) format
Date:Sun, 28 Apr 2019 21:50:45 + (UTC)
From:NetBSD Test Fixture
Message-ID: <155648824563.27186.9065778287415893...@babylon5.netbsd.org>
| The newly failing test case is:
|
| lib/libutil/t_snprintb:snprintb
I know what is happening with that, and I
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libutil/t_snprintb:snprintb
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
Fixed, thanks!
christos
> On Apr 7, 2019, at 8:32 AM, Rin Okuyama wrote:
>
> On 2019/04/07 1:00, Andreas Gustafsson wrote:
>> Christos Zoulas wrote:
>>> Must be, but I can't reproduce it, can you run gdb on the core file?
>> No need to go hunting or a core, simply running "date" with no
>>
On 2019/04/07 1:00, Andreas Gustafsson wrote:
Christos Zoulas wrote:
Must be, but I can't reproduce it, can you run gdb on the core file?
No need to go hunting or a core, simply running "date" with no
arguments will reproduce it. Doing that under gdb shows:
(gdb) where
#0 0xac643b67
Christos Zoulas wrote:
> Must be, but I can't reproduce it, can you run gdb on the core file?
No need to go hunting or a core, simply running "date" with no
arguments will reproduce it. Doing that under gdb shows:
(gdb) where
#0 0xac643b67 in ?? () from /lib/libc.so.12
#1 0xac644496 in
Must be, but I can't reproduce it, can you run gdb on the core file?
christos
> On Apr 6, 2019, at 3:52 AM, Andreas Gustafsson wrote:
>
> NetBSD Test Fixture wrote:
>> This is an automatically generated notice of new failures of the
>> NetBSD test suite.
>>
>> The newly failing test cases
NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> atf/tools/atf-run_test:broken_results
[...]
Looking at the log for the first failing test, "date" is dumping core:
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
atf/tools/atf-run_test:broken_results
atf/tools/atf-run_test:broken_tp_list
atf/tools/atf-run_test:exit_codes
atf/tools/atf-run_test:expect
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
atf/tools/atf-run_test:cleanup_mount
atf/tools/atf-run_test:cleanup_symlink
fs/tmpfs/t_create:attrs
fs/tmpfs/t_create:create
fs/tmpfs/t_create:kqueue
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/c++/t_cxxruntime:cxxruntime_pic_profile
usr.bin/c++/t_static_destructor:static_destructor_pic_profile
The above tests failed in each of the last 3 test runs, and
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/if_ipsec/t_ipsec_natt:ipsecif_natt_transport_null
net/npf/t_npf:npf_conn
net/npf/t_npf:npf_nat
net/npf/t_npf:npf_nbuf
net/npf/t_npf:npf_state
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/npf/t_npf:npf_bpf
The above test failed in each of the last 3 test runs, and passed in
at least 22 consecutive runs before that.
The following commits were made between
In article <23645.7935.238592.235...@guava.gson.org>,
Andreas Gustafsson wrote:
>The NetBSD Test Fixture wrote:
>> The newly failing test cases are:
>>
>> dev/raidframe/t_raid:raid1_comp0fail
>> dev/raidframe/t_raid:raid1_compfail
>> dev/raidframe/t_raid:raid1_normal
>>
The NetBSD Test Fixture wrote:
> The newly failing test cases are:
>
> dev/raidframe/t_raid:raid1_comp0fail
> dev/raidframe/t_raid:raid1_compfail
> dev/raidframe/t_raid:raid1_normal
> dev/raidframe/t_raid:raid5_compfail
> dev/raidframe/t_raid:raid5_normal
This was a duplicate
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
dev/raidframe/t_raid:raid1_comp0fail
dev/raidframe/t_raid:raid1_compfail
dev/raidframe/t_raid:raid1_normal
dev/raidframe/t_raid:raid5_compfail
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
dev/raidframe/t_raid:old_numrows_config
dev/raidframe/t_raid:smalldisk
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
dev/raidframe/t_raid:raid1_comp0fail
dev/raidframe/t_raid:raid1_compfail
dev/raidframe/t_raid:raid1_normal
dev/raidframe/t_raid:raid5_compfail
The NetBSD Test Fixture wrote:
> The newly failing test cases are:
>
> lib/libc/sys/t_ptrace_wait3:dbregs_dr0_dont_inherit_execve
> lib/libc/sys/t_ptrace_wait3:dbregs_dr0_dont_inherit_lwp
(etc, more than 300 failing test cases)
These are also failing on real i386 hardware, but not on
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libc/sys/t_ptrace_wait3:dbregs_dr0_dont_inherit_execve
lib/libc/sys/t_ptrace_wait3:dbregs_dr0_dont_inherit_lwp
lib/libc/sys/t_ptrace_wait3:dbregs_dr0_trap_code
The NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> usr.bin/c++/t_asan_poison:poison
> usr.bin/c++/t_asan_poison:poison_pic
> usr.bin/cc/t_asan_poison:poison
>
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/c++/t_asan_poison:poison
usr.bin/c++/t_asan_poison:poison_pic
usr.bin/cc/t_asan_poison:poison
usr.bin/cc/t_asan_poison:poison_pic
The above tests failed
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/c++/t_asan_poison:poison
usr.bin/c++/t_asan_poison:poison_pic
usr.bin/cc/t_asan_poison:poison
usr.bin/cc/t_asan_poison:poison_pic
The above tests failed
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/net/getaddrinfo/t_getaddrinfo:empty_servname
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The
The NetBSD Test Fixture wrote:
> This is an automatically generated notice of a new failure of the
> NetBSD test suite.
>
> The newly failing test case is:
>
> sbin/gpt/t_gpt:migrate_disklabel
This was a false alarm - sorry about that. Looks like the testbed
used some idle time to fill in
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
sbin/gpt/t_gpt:migrate_disklabel
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
Between the last successful
Michael van Elst wrote:
> I have reverted that part of the commit that introduced that change.
> Lets find out if that makes the test succeed in the testbed again (it
> always succeeded here on real hardware). Then fix the test.
Reverting did make the lib/libc/sys/t_sendmmsg/sendmmsg_basic test
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libcurses/t_curses:background
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
On Fri, Nov 30, 2018 at 03:43:23PM +0100, Martin Husemann wrote:
> This test has hung for me (untill atf timeout) on some machines (e.g.
> single core arm) since several weeks, I think the test code is buggy.
While the test is buggy, the bug was triggered by the changed scheduler
behaviour.
I
On Fri, Nov 30, 2018 at 03:16:00PM +0200, Andreas Gustafsson wrote:
> The NetBSD Test Fixture wrote:
> > This is an automatically generated notice of a new failure of the
> > NetBSD test suite.
> >
> > The newly failing test case is:
> >
> > lib/libc/sys/t_sendmmsg:sendmmsg_basic
This test
The NetBSD Test Fixture wrote:
> This is an automatically generated notice of a new failure of the
> NetBSD test suite.
>
> The newly failing test case is:
>
> lib/libc/sys/t_sendmmsg:sendmmsg_basic
Sorry about the duplicate reports about this, that was an error on my
part which should now
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/sys/t_sendmmsg:sendmmsg_basic
The above test failed in each of the last 7 test runs, and passed in
at least 23 consecutive runs before that.
The following commits
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/sys/t_sendmmsg:sendmmsg_basic
The above test failed in each of the last 5 test runs, and passed in
at least 25 consecutive runs before that.
The following commits
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libc/sys/t_sendmmsg:sendmmsg_basic
The above test failed in each of the last 3 test runs, and passed in
at least 26 consecutive runs before that.
The following commits
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
kernel/t_sysv:msg
net/net/t_unix:sockaddr_un_local_peereid
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/c++/t_asan_poison:poison_pie
usr.bin/cc/t_asan_poison:poison_pie
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/net/t_forwarding:ipforwarding_fastforward_v4
net/net/t_forwarding:ipforwarding_fastforward_v6
net/net/t_forwarding:ipforwarding_fragment_v4
Date:Mon, 19 Nov 2018 01:07:17 + (UTC)
From:NetBSD Test Fixture
Message-ID: <154258963726.7846.5173440576646830...@babylon5.netbsd.org>
| The newly failing test case is:
| bin/sh/t_patterns:case_matching
This is expected - the failures are from newly
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
bin/sh/t_patterns:case_matching
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
Robert Elz wrote:
> | The newly failing test case is:
> |
> | sbin/gpt/t_gpt:migrate_disklabel
[...]
> That leaves mrg's gcc changes, and if gcc has started generating bad code for
> (the fairly simple source that is) fdisk (or for dd, which makes a filesys
> image via a copy from
Date:Mon, 12 Nov 2018 21:54:55 + (UTC)
From:NetBSD Test Fixture
Message-ID: <154205969552.20934.15305308438594495...@babylon5.netbsd.org>
| The newly failing test case is:
|
| sbin/gpt/t_gpt:migrate_disklabel
The issue is fdisk writing messages to
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
sbin/gpt/t_gpt:migrate_disklabel
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
Between the last successful
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
kernel/t_trapsignal:fpe_handle
kernel/t_trapsignal:fpe_handle_recurse
kernel/t_trapsignal:fpe_ignore
kernel/t_trapsignal:fpe_mask
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libm/t_cos:cosf_angles
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
Between the last successful test
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/npf/t_npf:npf_bpf
net/npf/t_npf:npf_nat
net/npf/t_npf:npf_nbuf
net/npf/t_npf:npf_rule
net/npf/t_npf:npf_state
net/npf/t_npf:npf_table
The above tests
In article <20181026003810.d7e3617f...@rebar.astron.com>,
Christos Zoulas wrote:
>On Oct 24, 2:14pm, mar...@netbsd.org (Martin Husemann) wrote:
>-- Subject: Re: Automated report: NetBSD-current/i386 test failure
>
>| Ktraceing it shows the failing call is sendmsg() - which
On Oct 24, 2:14pm, mar...@netbsd.org (Martin Husemann) wrote:
-- Subject: Re: Automated report: NetBSD-current/i386 test failure
| Ktraceing it shows the failing call is sendmsg() - which should be properly
| intercepted by librumphijack, but talks to the host kernel and gets errno 32
On Sun, Sep 30, 2018 at 06:13:41PM +, NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> net/ipsec/t_ipsec_natt:ipsec_natt_transport_null
>
The NetBSD Test Fixture wrote:
> net/if_pppoe/t_pppoe:pppoe6_chap
>
> The above test failed in each of the last 3 test runs, and passed in
> at least 21 consecutive runs before that.
Looks like this happened by chance. Here are the outcomes of the last
100 runs, with success marked by "-"
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
net/if_pppoe/t_pppoe:pppoe6_chap
The above test failed in each of the last 3 test runs, and passed in
at least 21 consecutive runs before that.
The following commits were
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libcurses/t_curses:background
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
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/ipsec/t_ipsec_natt:ipsec_natt_transport_null
net/ipsec/t_ipsec_natt:ipsec_natt_transport_rijndaelcbc
The above tests failed in each of the last 3 test runs, and
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
Sorry, if my app sends it as html, I don’t have access to my regular machine at the moment.04.09.2018, 16:38, "NetBSD Test Fixture" :This is an automatically generated notice of new failures of theNetBSD test suite.The newly failing test cases are:lib/libbpfjit/t_bpfjit:libbpfjit_bad_ret_k
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
usr.bin/cc/t_hello:hello_profile
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
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
lib/libbpfjit/t_bpfjit:libbpfjit_bad_ret_k
lib/libbpfjit/t_bpfjit:libbpfjit_cop_no_ctx
lib/libbpfjit/t_bpfjit:libbpfjit_copx_no_ctx
201 - 300 of 401 matches
Mail list logo
