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 consecutiv
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 newly failing test cases
I am seeing a bunch of generated files related to sys/rump and libbozohttp (or
something ... see below) recently. These should be in the object directory.
I have an up to date tree (the messages below are from cvs-update) - I delete
all these files, build again, and they reappear
I' kind of
On May 7, 12:11am, k...@munnari.oz.au (Robert Elz) wrote:
-- Subject: Recent spew into SRCDIR from build.sh
| I am seeing a bunch of generated files related to sys/rump and libbozohttp (or
| something ... see below) recently. These should be in the object directory.
|
| I have an up to date tre
Date:Sun, 6 May 2018 13:44:22 -0400
From:chris...@zoulas.com (Christos Zoulas)
Message-ID: <20180506174422.52cd817f...@rebar.astron.com>
| Sure, but I don't see this...
It might depend on options to build.sh ... I use:
env -i \
"PATH=/sbin:/bin:/usr
Java-based console on one of my servers is so bad I can't enter
a passphrase correctly unless it echoed. The new -e option does
exactly this:
# cgdconfig -eC
/dev/wd0f's passphrase (echo):123456
While I was there I also changed a couple of small things:
- If a local buffer isn't long enough for
On Mon, 7 May 2018, Robert Elz wrote:
I am seeing a bunch of generated files related to sys/rump and libbozohttp (or
something ... see below) recently. These should be in the object directory.
I have an up to date tree (the messages below are from cvs-update) - I delete
all these files, build
Date:Sun, 6 May 2018 13:44:22 -0400
From:chris...@zoulas.com (Christos Zoulas)
Message-ID: <20180506174422.52cd817f...@rebar.astron.com>
| Sure, but I don't see this...
Apologies - forget it for now, and sorry for wasting your time.I suspect
that over use of -o
On May 7, 4:24am, k...@munnari.oz.au (Robert Elz) wrote:
-- Subject: Re: Recent spew into SRCDIR from build.sh
| Date:Sun, 6 May 2018 13:44:22 -0400
| From:chris...@zoulas.com (Christos Zoulas)
| Message-ID: <20180506174422.52cd817f...@rebar.astron.com>
|
| | Sure,
Date:Mon, 7 May 2018 05:07:21 +0800 (+08)
From:Paul Goyette
Message-ID:
| One of the benefits of using a read-only $SRCDIR is prevention of this
| sort of thing. :)
Yes, I know, I used to do that (and still do for stable builds) but when
I'm constantly updati
On Mon, 7 May 2018, Robert Elz wrote:
I've considered putting a read only unionfs mount on top of srcdir, and
then use that as the source directory, but I haven't tested that to see
how well (if at all) that would work.
I use a null mount for src_ro on top of src. Updates get done in
the src
Date:Sun, 6 May 2018 17:34:30 -0400
From:chris...@zoulas.com (Christos Zoulas)
Message-ID: <20180506213430.5edd117f...@rebar.astron.com>
| Perhaps it is faster to have make(1) do it automatically, but that's too
weird and
| fragile.
Agreed, I'd never suggest that
Updating src tree:
P src/external/gpl3/binutils/dist/bfd/elflink.c
P src/external/gpl3/binutils/dist/ld/emultempl/elf32.em
P src/sbin/cgdconfig/cgdconfig.c
P src/share/man/man3lua/bozohttpd.3lua
P src/sys/arch/arm/dts/sun50i-a64-pinebook.dts
P src/sys/arch/arm/dts/sun50i-a64.dtsi
P src/sys/arch/ar
13 matches
Mail list logo
