Automated report: NetBSD-current/i386 test failure

2018-08-25 Thread NetBSD Test Fixture
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 22 consecutive runs before that. The following commits were

Automated report: NetBSD-current/i386 test failure

2018-08-24 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: dev/audio/t_pad:pad_output 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

Automated report: NetBSD-current/i386 test failure

2018-07-28 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/stdlib/t_posix_memalign:aligned_alloc_basic The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The

Re: Automated report: NetBSD-current/i386 test failure

2018-07-16 Thread Kamil Rytarowski
On 15.07.2018 23:08, Kamil Rytarowski wrote: > On 15.07.2018 19:24, Andreas Gustafsson wrote: >> The NetBSD Test Fixture wrote: >>> The newly failing test cases are: >>> >>> usr.bin/c++/t_asan_double_free:double_free_profile >>>

Re: Automated report: NetBSD-current/i386 test failure

2018-07-15 Thread Kamil Rytarowski
On 15.07.2018 19:24, Andreas Gustafsson wrote: > The NetBSD Test Fixture wrote: >> The newly failing test cases are: >> >> usr.bin/c++/t_asan_double_free:double_free_profile >> usr.bin/c++/t_asan_global_buffer_overflow:global_buffer_overflow_profile >>

Re: Automated report: NetBSD-current/i386 test failure

2018-07-15 Thread Andreas Gustafsson
The NetBSD Test Fixture wrote: > The newly failing test cases are: > > usr.bin/c++/t_asan_double_free:double_free_profile > usr.bin/c++/t_asan_global_buffer_overflow:global_buffer_overflow_profile > usr.bin/c++/t_asan_heap_overflow:heap_overflow_profile >

Automated report: NetBSD-current/i386 test failure

2018-07-14 Thread NetBSD Test Fixture
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_double_free:double_free_profile usr.bin/c++/t_asan_global_buffer_overflow:global_buffer_overflow_profile

Automated report: NetBSD-current/i386 test failure

2018-07-06 Thread NetBSD Test Fixture
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_cache_overwriting net/arp/t_arp:arp_command net/arp/t_arp:arp_proxy_arp_pub net/arp/t_arp:arp_proxy_arp_pubproxy The above tests failed in each

Automated report: NetBSD-current/i386 test failure

2018-06-11 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow_pic usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow_pie

Automated report: NetBSD-current/i386 test failure

2018-06-07 Thread NetBSD Test Fixture
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:traceme_vfork_crash_bus The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The

Automated report: NetBSD-current/i386 test failure

2018-05-31 Thread NetBSD Test Fixture
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:traceme_vfork_crash_bus lib/libc/sys/t_ptrace_wait4:traceme_vfork_crash_bus lib/libc/sys/t_ptrace_wait6:traceme_vfork_crash_bus

Automated report: NetBSD-current/i386 test failure

2018-05-29 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/nfs/t_rquotad:get_nfs_be_1_both fs/nfs/t_rquotad:get_nfs_be_1_group fs/nfs/t_rquotad:get_nfs_be_1_user fs/nfs/t_rquotad:get_nfs_le_1_both

Automated report: NetBSD-current/i386 test failure

2018-05-22 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: kernel/t_trapsignal:trap_handle kernel/t_trapsignal:trap_handle_recurse kernel/t_trapsignal:trap_mask kernel/t_trapsignal:trap_simple The above tests failed in

Re: Automated report: NetBSD-current/i386 test failure

2018-05-06 Thread Robert Elz
Date:Sun, 6 May 2018 09:51:37 + (UTC) From:NetBSD Test Fixture Message-ID: <152560029739.5273.3538625001371879...@babylon5.netbsd.org> | This is an automatically generated notice of new failures of the | NetBSD test suite. | | The

Automated report: NetBSD-current/i386 test failure

2018-05-06 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: dev/cgd/t_cgd:basic dev/cgd/t_cgd:unaligned_write dev/cgd/t_cgd:wrongpass The above tests failed in each of the last 3 test runs, and passed in at least 27

Re: Automated report: NetBSD-current/i386 test failure

2018-04-25 Thread Martin Husemann
I added a bit of debug to the test and exctracted a pcap dump. Below is a tcpdump after 5 seconds of waiting for RAs, also attached is a pcap file with all traffic untill I stopped the test. Martin tps-count: 1 tp-start: 1524644478.732840, t_ra, 10 tc-start: 1524644478.732883, ra_basic

Automated report: NetBSD-current/i386 test failure

2018-04-25 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/net/t_ping6_opts:ping6_opts_hops 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

Re: Automated report: NetBSD-current/i386 test failure

2018-04-24 Thread Martin Husemann
On Tue, Apr 24, 2018 at 05:38:12PM +0100, Roy Marples wrote: > Maybe the kernel is rejecting the RA somehow? No, it isn't. On a system where it all works, just updating rtadvd (and rump.rtadvd) breaks the test. Martin

Re: Automated report: NetBSD-current/i386 test failure

2018-04-24 Thread Roy Marples
On 24/04/2018 15:27, Martin Husemann wrote: On Mon, Apr 23, 2018 at 08:51:52AM +, 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/ndp/t_ra:ra_basic [..] 2018.04.20.11.25.39 roy

Re: Automated report: NetBSD-current/i386 test failure

2018-04-24 Thread Martin Husemann
On Mon, Apr 23, 2018 at 08:51:52AM +, 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/ndp/t_ra:ra_basic [..] > 2018.04.20.11.25.39 roy src/usr.sbin/rtadvd/rtadvd.c,v 1.63

Automated report: NetBSD-current/i386 test failure

2018-04-23 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/ndp/t_ra:ra_basic net/ndp/t_ra:ra_defrouter_expiration net/ndp/t_ra:ra_delete_address net/ndp/t_ra:ra_flush_defrouter_entries

Automated report: NetBSD-current/i386 test failure

2018-04-18 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: dev/scsipi/t_cd:noisyeject net/if_loop/t_pr:loopmtu net/if_loop/t_pr:loopmtu_csum The above tests failed in each of the last 3 test runs, and passed in at least 27

Automated report: NetBSD-current/i386 test failure

2018-03-25 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/icmp/t_ping:ping_of_death 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

Automated report: NetBSD-current/i386 test failure

2018-03-22 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/icmp/t_ping:floodping2 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

Automated report: NetBSD-current/i386 test failure

2018-03-22 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/icmp/t_ping:floodping net/icmp/t_ping:pingsize The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The

Automated report: NetBSD-current/i386 test failure

2018-03-20 Thread NetBSD Test Fixture
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_recvmmsg:recvmmsg_basic 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

Automated report: NetBSD-current/i386 test failure

2018-03-10 Thread NetBSD Test Fixture
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:ipsecif_basic_ipv4overipv6_esp_null net/if_ipsec/t_ipsec:ipsecif_basic_ipv4overipv6_esp_rijndaelcbc

Automated report: NetBSD-current/i386 test failure

2018-03-07 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/ndp/t_dad:dad_basic net/ndp/t_dad:dad_count The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The

Automated report: NetBSD-current/i386 test failure

2018-02-11 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_certs:x509v3 crypto/libcrypto/t_ciphers:evp crypto/libcrypto/t_ciphers:idea crypto/libcrypto/t_hashes:sha

Automated report: NetBSD-current/i386 test failure

2018-02-09 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/psshfs/t_psshfs:inode_nos fs/psshfs/t_psshfs:ls fs/psshfs/t_psshfs:pwd fs/psshfs/t_psshfs:read_empty_file The above tests failed in each of the last 3 test

Automated report: NetBSD-current/i386 test failure

2018-02-07 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/icmp/t_ping:ping_of_death 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

Automated report: NetBSD-current/i386 test failure

2018-02-06 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/net/t_ping_opts:ping_opts_gateway net/net/t_ping_opts:ping_opts_recordroute The above tests failed in each of the last 3 test runs, and passed in at least 27

Automated report: NetBSD-current/i386 test failure

2018-01-27 Thread NetBSD Test Fixture
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_pap The above test failed in each of the last 3 test runs, and passed in at least 25 consecutive runs before that. The following commits were

Automated report: NetBSD-current/i386 test failure

2018-01-09 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/nfs/t_rquotad:get_nfs_be_1_both fs/nfs/t_rquotad:get_nfs_be_1_group fs/nfs/t_rquotad:get_nfs_be_1_user fs/nfs/t_rquotad:get_nfs_le_1_both

Re: Automated report: NetBSD-current/i386 test failure

2018-01-08 Thread Andreas Gustafsson
Hi maxv, On Jan 2, the NetBSD Test Fixture wrote: > The newly failing test cases are: > > net/can/t_canfilter:canfilter_get > net/can/t_canfilter:canfilter_null > net/ipsec/t_ipsec_tunnel_odd:ipsec_tunnel_v6v4_ah_aesxcbcmac >

Automated report: NetBSD-current/i386 test failure

2018-01-02 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/can/t_canfilter:canfilter_get net/can/t_canfilter:canfilter_null net/ipsec/t_ipsec_tunnel_odd:ipsec_tunnel_v6v4_ah_aesxcbcmac

Re: Automated report: NetBSD-current/i386 test failure

2017-12-13 Thread Ryota Ozaki
On Wed, Dec 13, 2017 at 9:27 PM, Andreas Gustafsson wrote: > NetBSD Test Fixture wrote: >> The newly failing test cases are: >> >> fs/vfs/t_mtime_otrunc:puffs_otrunc_mtime_update >> net/route/t_change:route_change_ifp >> net/route/t_change:route_change_ifp_ifa >> >> The

Re: Automated report: NetBSD-current/i386 test failure

2017-12-13 Thread Andreas Gustafsson
NetBSD Test Fixture wrote: > The newly failing test cases are: > > fs/vfs/t_mtime_otrunc:puffs_otrunc_mtime_update > net/route/t_change:route_change_ifp > net/route/t_change:route_change_ifp_ifa > > The above tests failed in each of the last 3 test runs, and passed in > at least 27

Re: Automated report: NetBSD-current/i386 test failure

2017-12-12 Thread Frank Kardel
That may also be related with the symptoms I see when booting 8.99.9 on amd64 while dhcpcd attempts to solicit a router - it gets stuck in route code on psref_release() - needless to say the machine is wedged at that point. Frank db{0}> mach cpu 1 using CPU 1 db{0}> bt psref_release() at

Automated report: NetBSD-current/i386 test failure

2017-12-12 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/vfs/t_mtime_otrunc:puffs_otrunc_mtime_update net/route/t_change:route_change_ifp net/route/t_change:route_change_ifp_ifa The above tests failed in each of the

Automated report: NetBSD-current/i386 test failure

2017-12-11 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_hmacsha512 net/ipsec/t_ipsec_l2tp:ipsec_l2tp_ipv4_transport_ah_null The above tests failed in each of the last 3 test

Re: Automated report: NetBSD-current/i386 test failure

2017-12-07 Thread Robert Elz
Date:Thu, 7 Dec 2017 10:06:57 + (UTC) From:NetBSD Test Fixture Message-ID: <151264121702.11938.4866008250470225...@babylon5.netbsd.org> | The newly failing test case is: | lib/libc/gen/t_fmtcheck:fmtcheck_basic This was a faulty

Automated report: NetBSD-current/i386 test failure

2017-12-07 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/gen/t_fmtcheck:fmtcheck_basic 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

Automated report: NetBSD-current/i386 test failure

2017-12-01 Thread NetBSD Test Fixture
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:threads 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

Re: Automated report: NetBSD-current/i386 test failure

2017-11-30 Thread Robert Elz
Date:Thu, 30 Nov 2017 14:14:54 + (UTC) From:chris...@astron.com (Christos Zoulas) Message-ID: | I forgot to fix the test; yes the previous test was wrong | and the current output is correct. Not a problem, my local copy of

Re: Automated report: NetBSD-current/i386 test failure

2017-11-30 Thread Christos Zoulas
In article <23364.1512023...@andromeda.noi.kre.to>, Robert Elz wrote: >Date:Wed, 29 Nov 2017 02:48:22 + (UTC) >From:NetBSD Test Fixture >Message-ID: <151192370231.10146.3070298657628695...@babylon5.netbsd.org> > > | The

Re: Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread Robert Elz
Date:Wed, 29 Nov 2017 02:48:22 + (UTC) From:NetBSD Test Fixture Message-ID: <151192370231.10146.3070298657628695...@babylon5.netbsd.org> | The newly failing test case is: | lib/libc/locale/t_strfmon:strfmon I have been looking into

Re: Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread Robert Elz
Date:Wed, 29 Nov 2017 19:52:16 + (UTC) From:NetBSD Test Fixture Message-ID: <151198513515.5439.11050507388623818...@babylon5.netbsd.org> | The newly failing test case is: | | lib/libc/locale/t_sprintf:strto See the thread on

Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/locale/t_sprintf:strto The above test failed in each of the last 3 test runs, and passed in at least 24 consecutive runs before that. The following commits were

Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread NetBSD Test Fixture
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:pppoe_chap 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

Automated report: NetBSD-current/i386 test failure

2017-11-28 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/locale/t_strfmon:strfmon 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

Re: Automated report: NetBSD-current/i386 test failure

2017-11-26 Thread Robert Elz
Date:Sun, 26 Nov 2017 17:27:43 + (UTC) From:NetBSD Test Fixture Message-ID: <151171726367.14929.15350427540173059...@babylon5.netbsd.org> | The newly failing test case is: | | net/ndp/t_ra:ra_flush_prefix_entries This one is mine.

Automated report: NetBSD-current/i386 test failure

2017-11-26 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/ndp/t_ra:ra_flush_prefix_entries 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

Re: Automated report: NetBSD-current/i386 test failure

2017-11-22 Thread Robert Elz
Date:Thu, 23 Nov 2017 03:47:54 + (UTC) From:NetBSD Test Fixture Message-ID: <151140887413.3239.7965355474725373...@babylon5.netbsd.org> | The newly failing test cases are: | | net/if_vlan/t_vlan:vlan_vlanid |

Automated report: NetBSD-current/i386 test failure

2017-11-22 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/if_vlan/t_vlan:vlan_vlanid net/if_vlan/t_vlan:vlan_vlanid6 The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before

Re: Automated report: NetBSD-current/i386 test failure

2017-11-21 Thread Robert Elz
Date:Tue, 21 Nov 2017 16:24:11 + (UTC) From:NetBSD Test Fixture Message-ID: <151128145157.6814.10978947665640174...@babylon5.netbsd.org> | The newly failing test cases are: | | dev/raidframe/t_raid:raid1_comp0fail |

Automated report: NetBSD-current/i386 test failure

2017-11-21 Thread NetBSD Test Fixture
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

Re: Automated report: NetBSD-current/i386 test failure

2017-11-15 Thread Riccardo Mottola
Hi, Martin Husemann wrote: This was fallout fromt the gcc import, it should be fixed now.  suppose they caused the build failure of tools the 13th forme. Build fine again yesterday. Rebuilding distribution currently. Riccardo

Re: Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread Rin Okuyama
On 2017/11/14 23:09, Martin Husemann wrote: On Tue, Nov 14, 2017 at 01:58:54PM +, NetBSD Test Fixture wrote: This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: This was fallout fromt the gcc import, it should be fixed

Re: Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread Martin Husemann
On Tue, Nov 14, 2017 at 01:58:54PM +, NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: This was fallout fromt the gcc import, it should be fixed now. Martin

Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: share/mk/t_lib:defaults__build_and_install share/mk/t_prog:defaults__build_and_install share/mk/t_prog:without_man__build_and_install share/mk/t_test:one_c

Re: Automated report: NetBSD-current/i386 test failure

2017-10-27 Thread Robert Elz
Date:Thu, 26 Oct 2017 11:02:13 +0700 From:Robert Elz Message-ID: <9015.1508990...@andromeda.noi.kre.to> | lib/libc/time/t_mktime:mktime_negyear | To me it looks like it is a bogus test, and I have no idea how it | ever worked. I have

Re: Automated report: NetBSD-current/i386 test failure

2017-10-27 Thread Robert Elz
Date:Wed, 25 Oct 2017 17:52:52 + (UTC) From:NetBSD Test Fixture Message-ID: <150895397201.5616.843588977796354...@babylon5.netbsd.org> | The newly failing test cases are: | | lib/libc/time/t_mktime:mktime_negyear |

Re: Automated report: NetBSD-current/i386 test failure

2017-10-26 Thread Martin Husemann
On Thu, Oct 26, 2017 at 11:02:13AM +0700, Robert Elz wrote: > errno = 0; > t = mktime(); > ATF_REQUIRE_ERRNO(0, t != (time_t)-1); I guess the author meant to write: errno = 0; t = mktime(); ATF_REQUIRE(errno == 0; ATF_REQUIRE(t !=

Re: Automated report: NetBSD-current/i386 test failure

2017-10-25 Thread Robert Elz
Date:Wed, 25 Oct 2017 17:52:52 + (UTC) From:NetBSD Test Fixture Message-ID: <150895397201.5616.843588977796354...@babylon5.netbsd.org> | The newly failing test cases are: | | lib/libc/time/t_mktime:mktime_negyear I have been

Re: Automated report: NetBSD-current/i386 test failure

2017-10-25 Thread Robert Elz
Date:Wed, 25 Oct 2017 17:52:52 + (UTC) From:NetBSD Test Fixture Message-ID: <150895397201.5616.843588977796354...@babylon5.netbsd.org> | This is an automatically generated notice of new failures of the | NetBSD test suite. | | The

Automated report: NetBSD-current/i386 test failure

2017-10-25 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: lib/libc/time/t_mktime:mktime_negyear lib/libc/time/t_mktime:timegm_epoch lib/libc/time/t_strptime:Zone lib/libc/time/t_strptime:zone

Automated report: NetBSD-current/i386 test failure

2017-10-09 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/tls/t_tls_static:t_tls_static 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

Re: Automated report: NetBSD-current/i386 test failure

2017-09-20 Thread Robert Elz
Date:Wed, 20 Sep 2017 21:06:51 + (UTC) From:NetBSD Test Fixture Message-ID: <150594161124.25268.1441500354190307...@babylon5.netbsd.org> | This is an automatically generated notice of new failures of the | NetBSD test suite. | | The

Automated report: NetBSD-current/i386 test failure

2017-09-20 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: bin/dd/t_dd:seek fs/tmpfs/t_create:attrs fs/tmpfs/t_devices:basic fs/tmpfs/t_link:basic fs/tmpfs/t_link:subdirs fs/tmpfs/t_mkdir:attrs

Automated report: NetBSD-current/i386 test failure

2017-09-07 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: 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

Automated report: NetBSD-current/i386 test failure

2017-07-25 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: kernel/t_extent:subregion1 kernel/t_extent:subregion2 kernel/t_extent:subregion3 kernel/t_extent:subregion4 The above tests failed in each of the last 3 test

Automated report: NetBSD-current/i386 test failure

2017-06-27 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/route/t_flags6:route_flags_blackhole6 The above test failed in each of the last 4 test runs, and passed in at least 26 consecutive runs before that. The following

Re: Automated report: NetBSD-current/i386 test failure

2017-05-09 Thread Andreas Gustafsson
On May 7, 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: > > lib/libc/sys/t_clone:clone_basic > lib/libc/sys/t_clone:clone_null_func There is also a new failure of

Automated report: NetBSD-current/i386 test failure

2017-05-07 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: lib/libc/sys/t_clone:clone_basic lib/libc/sys/t_clone:clone_null_func The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs

Re: Automated report: NetBSD-current/i386 test failure

2017-04-22 Thread Robert Elz
Date:Sat, 22 Apr 2017 06:08:07 + (UTC) From:NetBSD Test Fixture Message-ID: <149284128755.18726.798491142241052...@babylon5.netbsd.org> | The newly failing test case is: | | lib/librumphijack/t_vfs:ln_nox | | The above test

Automated report: NetBSD-current/i386 test failure

2017-04-22 Thread NetBSD Test Fixture
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

Automated report: NetBSD-current/i386 test failure

2017-03-19 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/vfs/t_full:lfs_fillfs fs/vfs/t_io:lfs_overwrite_trunc fs/vfs/t_io:lfs_shrinkfile fs/vfs/t_io:lfs_wrrd_after_unlink fs/vfs/t_renamerace:lfs_renamerace_dirs

Re: Automated report: NetBSD-current/i386 test failure

2017-03-03 Thread Andreas Gustafsson
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/arp/t_dad:dad_basic > net/ndp/t_ra:ra_multiple_routers_maxifprefixes Please take this particular report with a grain of salt.

Automated report: NetBSD-current/i386 test failure

2017-03-03 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/arp/t_dad:dad_basic net/ndp/t_ra:ra_multiple_routers_maxifprefixes The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs

Automated report: NetBSD-current/i386 test failure

2017-02-17 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: sbin/sysctl/t_perm:sysctl_net 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

Automated report: NetBSD-current/i386 test failure

2017-02-11 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: dev/audio/t_pad:pad_output 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

Automated report: NetBSD-current/i386 test failure

2017-02-02 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/net/t_mtudisc6:mtudisc6_basic 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

Automated report: NetBSD-current/i386 test failure

2017-01-20 Thread NetBSD Test Fixture
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_nbuf net/npf/t_npf:npf_state The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The

Automated report: NetBSD-current/i386 test failure

2017-01-15 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: lib/libc/ssp/t_ssp:fgets lib/libc/ssp/t_ssp:getcwd lib/libc/ssp/t_ssp:gets lib/libc/ssp/t_ssp:memcpy lib/libc/ssp/t_ssp:memmove lib/libc/ssp/t_ssp:memset

Automated report: NetBSD-current/i386 test failure

2017-01-10 Thread NetBSD Test Fixture
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_commands 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

Automated report: NetBSD-current/i386 test failure

2016-12-13 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/if_pppoe/t_pppoe:pppoe6_chap net/if_pppoe/t_pppoe:pppoe6_pap net/if_pppoe/t_pppoe:pppoe_pap The above tests failed in each of the last 4 test runs, and passed in

Automated report: NetBSD-current/i386 test failure

2016-12-09 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: dev/audio/t_pad:pad_output net/npf/t_npf:npf_table The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that.

Re: Automated report: NetBSD-current/i386 test failure

2016-11-17 Thread Paul Goyette
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: dev/scsipi/t_cd:noisyeject The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. This is mine. Under

Re: Automated report: NetBSD-current/i386 test failure

2016-11-17 Thread Paul Goyette
On Thu, 17 Nov 2016, 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: dev/scsipi/t_cd:noisyeject The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs

Automated report: NetBSD-current/i386 test failure

2016-11-17 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: dev/scsipi/t_cd:noisyeject 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

Automated report: NetBSD-current/i386 test failure

2016-11-12 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: kernel/t_ptrace_wait4:attach1 kernel/t_ptrace_wait6:attach1 kernel/t_ptrace_waitpid:attach1 The above tests failed in each of the last 4 test runs, and passed in at

Re: Automated report: NetBSD-current/i386 test failure

2016-11-06 Thread Paul Goyette
It would seem that the OOSIOCGIFBRDADDR ioctl is part of COMPAT_43. Yet the test runs in a rump environment, and rump only has COMPAT_50 and newer. So I would expect this test to fail. It didn't fail previously because we included sys/compat/common/if_43.c code all the time, rather than

Automated report: NetBSD-current/i386 test failure

2016-11-06 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if/t_compat:OOSIOCGIFBRDADDR 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

Automated report: NetBSD-current/i386 test failure

2016-10-01 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if_tun/t_tun:tun_setup The above test failed in each of the last 4 test runs, and passed in at least 26 consecutive runs before that. The following commits were made

Automated report: NetBSD-current/i386 test failure

2016-09-13 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/arp/t_dad:dad_duplicated net/if/t_ifconfig:ifconfig_parameters net/ndp/t_dad:dad_duplicated The above tests failed in each of the last 3 test runs, and passed in

Automated report: NetBSD-current/i386 test failure

2016-08-25 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libm/t_ldexp:ldexp_overflow 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

Automated report: NetBSD-current/i386 test failure

2016-08-18 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: usr.bin/xlint/lint1/t_integration:cast_lhs The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The following

Automated report: NetBSD-current/i386 test failure

2016-08-11 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/vfs/t_unpriv:ext2fs_dirperms fs/vfs/t_vnops:ext2fs_create_many fs/vfs/t_vnops:ext2fs_dir_rmdirdotdot fs/vfs/t_vnops:ext2fs_rename_dir

Re: Automated report: NetBSD-current/i386 test failure

2016-08-07 Thread Martin Husemann
On Sun, Aug 07, 2016 at 04:29:54PM +0700, Robert Elz wrote: > Alternatively, the man page could be changed to make EINVAL apply to > invalid (for any reason) addresses, and all mention of ENOMEM removed, > and the test updated (which would simplify it.) The man page and Posix agree on this, so

<    1   2   3   4   5   >