[automated-testing] Request for Aborting the job
Vijay Bhaskar Reddy Avuthu
vavuthu at redhat.com
Thu Jun 21 15:05:18 UTC 2018
Our BVT runs will take around ~6hrs which contains 118 Test cases (
excluding provisioning and upgrade time ).
Regarding each component, I am planning to take benchmarks and time-lines
On Thu, Jun 21, 2018 at 8:08 PM, Nigel Babu <nigelb at redhat.com> wrote:
> Hi Atin,
> This is not an answer I have at the moment from an upstream point of view.
> I know it takes more than 6h. Vijay, do you have the time taken from
> internal runs?
> On Thu, Jun 21, 2018 at 7:56 PM Atin Mukherjee <amukherj at redhat.com>
>> Off context question.
>> How much the entire glusto regression test suites take time to complete
>> at this moment? In future when we march towards a 100% automation would it
>> be realistic to have one complete glusto run to complete with every nightly
>> On Thu, 21 Jun 2018 at 19:50, Nigel Babu <nigelb at redhat.com> wrote:
>>> The test failure is the flag.
>>> On Thu, Jun 21, 2018 at 7:28 PM Sankarshan Mukhopadhyay <
>>> sankarshan.mukhopadhyay at gmail.com> wrote:
>>>> On Thu, Jun 21, 2018 at 7:11 PM, Nigel Babu <nigelb at redhat.com> wrote:
>>>> > I've been seeing two kinds of hangs that are causing this
>>>> > * Bad tests that take a lot of time and hang.
>>>> How are such tests flagged for improvements?
>>>> The test failure is the flag. In the past, these test runs would only
>>> be caught after the test has been merged. Now it will up to the test author
>>> to debug and bring the test time down to under 4h and not cause hangs.
>>> automated-testing mailing list
>>> automated-testing at gluster.org
>> - Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the automated-testing