Build failed in Jenkins: FreeBSD_HEAD-tests2 #670

See -- [...truncated 1016 lines...] lib/atf/libatf-c/macros_test:require_errno -> passed [0.034s] lib/atf/libatf-c/macros_test:require_match -> passed [0.041s] lib/atf/libatf-c/macros_test:requ

Jenkins build is unstable: FreeBSD_HEAD-tests2 #671

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Memory modified after free & Kernel panic with current (r278031)

Hallo, I'm still fighting with MinnowBoard... When I set the network interface I get a bunch of "Memory modified after free" messages. If I wait long enough (a couple of minutes) I get a kernel panic. Here an example with the dmesg (https://pastebin.mozilla.org/8657938) I've tested it using 10.1

[ZFS] [panic] Fatal trap 12: page fault while in kernel mode.

I do not know the conditions - it just happened. http://pastebin.com/BASJB599 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org

nagios vs w/uptime

[Moving to current@] On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote: > Surprises: > * nagios doesn't like w / uptime anymore. libxo perhaps? Seems most likely, although I haven’t seen any differences in output in my (admittedly limited) testing. In what way does Nagios not like w/uptime? Any c

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #672

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: nagios vs w/uptime

> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote: > > [Moving to current@] > >> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote: >> >> Surprises: >> * nagios doesn't like w / uptime anymore. libxo perhaps? > > Seems most likely, although I haven’t seen any differences in output > in my (a

Re: nagios vs w/uptime

> On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > >> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote: >> >> [Moving to current@] >> >>> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote: >>> >>> Surprises: >>> * nagios doesn't like w / uptime anymore. libxo perhaps? >> >> Seems

Re: nagios vs w/uptime

On Tue, 2015-02-10 at 22:24 +0100, Michael Gmelin wrote: > > > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > > > > > > >> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote: > >> > >> [Moving to current@] > >> > >>> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote: > >>> > >>> S

Re: nagios vs w/uptime

On Tue, 10 Feb 2015 22:24:59 +0100 Michael Gmelin wrote: > > > > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > > > > > > >> On 10 Feb 2015, at 21:13, Marcel Moolenaar > >> wrote: > >> > >> [Moving to current@] > >> > >>> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote: >

Re: nagios vs w/uptime

> > I wonder if that implies that any non-normal exit from a program that > has been xo'd will result in the loss of output that would not have been > lost before the xo changes? That could lead to all kinds of subtle > failures of existing scripts and apps. Well, so long as the app doesn't crash

[RFC] Removin the old make

Hi, I would like to start using bmake only syntax on our infrastructure for that I want to make sure noone is using the old make, so I plan to remove the old make from base, I plan to do it by Feb 16th. Note that bmake is the default since FreeBSD 10. FreeBSD 9.3 is also providing bmake (as bmake

Re: nagios vs w/uptime

On Tue, Feb 10, 2015 at 02:32:44PM -0700, Ian Lepore wrote: > On Tue, 2015-02-10 at 22:24 +0100, Michael Gmelin wrote: > > > > > > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > > > > > > > > > > > >> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote: > > >> > > >> [Moving to cur

Re: [RFC] Removin the old make

On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wrote: > Hi, > > I would like to start using bmake only syntax on our infrastructure for that I > want to make sure noone is using the old make, so I plan to remove the old > make > from base, I plan to do it by Feb 16th. How does

Re: [RFC] Removin the old make

On Wed, Feb 11, 2015 at 09:49:37AM +1100, Greg 'groggy' Lehey wrote: > On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wrote: > > Hi, > > > > I would like to start using bmake only syntax on our infrastructure for > > that I > > want to make sure noone is using the old make, so

Re: [RFC] Removin the old make

On Tue, 2015-02-10 at 23:59 +0100, Baptiste Daroussin wrote: > On Wed, Feb 11, 2015 at 09:49:37AM +1100, Greg 'groggy' Lehey wrote: > > On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wrote: > > > Hi, > > > > > > I would like to start using bmake only syntax on our infrastructure

Re: [RFC] Removin the old make

On Tue, Feb 10, 2015 at 04:04:16PM -0700, Ian Lepore wrote: > On Tue, 2015-02-10 at 23:59 +0100, Baptiste Daroussin wrote: > > On Wed, Feb 11, 2015 at 09:49:37AM +1100, Greg 'groggy' Lehey wrote: > > > On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wrote: > > > > Hi, > > > > > >

Re: [RFC] Removin the old make

On Tue, 10 Feb 2015 23:38:54 +0100 Baptiste Daroussin wrote > Hi, > > I would like to start using bmake only syntax on our infrastructure for that > I want to make sure noone is using the old make, so I plan to remove the old > make from base, I plan to do it by Feb 16th. Please note; I am not e

Re: [RFC] Removin the old make

On Tue, Feb 10, 2015 at 03:13:29PM -0800, Chris H wrote: > On Tue, 10 Feb 2015 23:38:54 +0100 Baptiste Daroussin wrote > > > Hi, > > > > I would like to start using bmake only syntax on our infrastructure for that > > I want to make sure noone is using the old make, so I plan to remove the old >

Re: [RFC] Removin the old make

On Wed, 11 Feb 2015 00:20:05 +0100 Baptiste Daroussin wrote > On Tue, Feb 10, 2015 at 03:13:29PM -0800, Chris H wrote: > > On Tue, 10 Feb 2015 23:38:54 +0100 Baptiste Daroussin > > wrote > > > Hi, > > > > > > I would like to start using bmake only syntax on our infrastructure for > > > that I

Re: nagios vs w/uptime

On Tue, 2015-02-10 at 22:55 +, Brooks Davis wrote: > On Tue, Feb 10, 2015 at 02:32:44PM -0700, Ian Lepore wrote: > > On Tue, 2015-02-10 at 22:24 +0100, Michael Gmelin wrote: > > > > > > > > > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > > > > > > > > > > > > > > > > >> On 10

Re: nagios vs w/uptime

On Tue, Feb 10, 2015 at 10:24:59PM +0100, Michael Gmelin wrote: > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote: > > > > Just compared 10.1 to current, unmodified output looks the same, but > > pipelines don't work properly: > > > > 10.1: > > # uptime | wc > > 1 12 68 > > > > Current: > > #

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #673

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

LOCAL_MTREE vs DB_FROM_SRC

(Apologies for google mail, I moved a while back and my office at home is still not up and hence my regular FreeBSD machine at home is also not up.) In Makefile.inc1 we have: .if defined(DB_FROM_SRC) INSTALLFLAGS+= -N ${.CURDIR}/etc MTREEFLAGS+= -N ${.CURDIR}/etc .endif which is fine as far as i

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #674

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #675

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"