Hi Sean,
Given the swift failure happened once in the available logstash recorded
history, do we still feel this is a major gate issue?
See:
On 01/24/2014 11:18 AM, Peter Portante wrote:
Hi Sean,
Given the swift failure happened once in the available logstash recorded
history, do we still feel this is a major gate issue?
See:
That's a pretty high rate of failure, and really needs investigation.
That's a great point, did you look into the logs of any of those jobs?
Thanks for bringing it to my attention.
I saw a few swift tests that would pop, I'll open bugs to look into those.
But the cardinality of the
On Fri, Jan 24, 2014 at 11:37 AM, Clay Gerrard clay.gerr...@gmail.com wrote:
That's a pretty high rate of failure, and really needs investigation.
That's a great point, did you look into the logs of any of those jobs?
Thanks for bringing it to my attention.
I saw a few swift tests that
Hi Sean,
In the last 7 days I see only 6 python27 based test failures:
On Fri, Jan 24, 2014, at 10:51 AM, John Griffith wrote:
On Fri, Jan 24, 2014 at 11:37 AM, Clay Gerrard clay.gerr...@gmail.com
wrote:
That's a pretty high rate of failure, and really needs investigation.
That's a great point, did you look into the logs of any of those jobs?
Thanks
On 01/24/2014 02:02 PM, Peter Portante wrote:
Hi Sean,
In the last 7 days I see only 6 python27 based test
failures:
On Fri, Jan 24, 2014 at 10:37 AM, Clay Gerrard clay.gerr...@gmail.comwrote:
That's a pretty high rate of failure, and really needs investigation.
That's a great point, did you look into the logs of any of those jobs?
Thanks for bringing it to my attention.
I saw a few swift tests that
OH yeah that's much better. I had found those eventually but had to dig
through all that other stuff :'(
Moving forward I think we can keep an eye on that page, open bugs for those
tests causing issue and dig in.
Thanks again!
-Clay
On Fri, Jan 24, 2014 at 11:37 AM, Sean Dague s...@dague.net
I've found out that several jobs are exhibiting failures like bug 1254890
[1] and bug 1253896 [2] because openvswitch seem to be crashing the kernel.
The kernel trace reports as offending process usually either
neutron-ns-metadata-proxy or dnsmasq, but [3] seem to clearly point to
ovs-vsctl.
254
On Fri, Jan 24, 2014 at 6:57 PM, Salvatore Orlando sorla...@nicira.comwrote:
I've found out that several jobs are exhibiting failures like bug 1254890
[1] and bug 1253896 [2] because openvswitch seem to be crashing the kernel.
The kernel trace reports as offending process usually either
* Salvatore Orlando (sorla...@nicira.com) wrote:
I've found out that several jobs are exhibiting failures like bug 1254890
[1] and bug 1253896 [2] because openvswitch seem to be crashing the kernel.
The kernel trace reports as offending process usually either
neutron-ns-metadata-proxy or
12 matches
Mail list logo
