----- Original Message -----
> ----- Original Message -----
> > I'm seeing 2 failure signatures.
> >
> > .out.bad files attached
> >
> > Any help would be appreciated as I have no clue what this test is or
> > should be doing.
>
> This test is exercising the new pcp2influxdb(1) command. There should
> be a 1111.full associated with these failures, which I think we'll need
>
I've attached a .full from one of my local runs where it's passing - Alec,
I notice there's several stacktraces there - is that due to socat closing
the connection (rather than the client)?
We might want to have some cleaner error reporting in pcp2influxdb there -
I guess it is feasible influxdb could restart and cause the same trace? If
so a less alarming end-user diagnostic would be preferable.
cheers.
--
Nathan
1111.full
Description: Binary data
|