On 7/25/2018 1:46 AM, Ghanshyam Mann wrote:
As per avg time, I have voted (currently based on 14 days avg) on ethercalc which
all test to mark as slow. I taken the criteria of >120 sec avg time. Once we
have more and more people votes there we can mark them slow.
On Wed, 25 Jul 2018 22:22:24 +0900 Matt Riedemann
wrote
> On 7/25/2018 1:46 AM, Ghanshyam Mann wrote:
> > yeah, there are many tests taking too long time. I do not know the reason
> > this time but last time we did audit for slow tests was mainly due to ssh
> > failure.
> >
On 7/25/2018 1:46 AM, Ghanshyam Mann wrote:
yeah, there are many tests taking too long time. I do not know the reason this
time but last time we did audit for slow tests was mainly due to ssh failure.
I have created the similar ethercalc [3] to collect time taking tests and then
round figure
On Wed, 25 Jul 2018 05:15:53 +0900 Matt Riedemann
wrote
> While going through our uncategorized gate failures [1] I found that we
> have a lot of jobs failing (161 in 7 days) due to the tempest run timing
> out [2]. I originally thought it was just the networking scenario tests,
While going through our uncategorized gate failures [1] I found that we
have a lot of jobs failing (161 in 7 days) due to the tempest run timing
out [2]. I originally thought it was just the networking scenario tests,
but I was able to identify a handful of API tests that are also taking
