hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15651) Track our flaky tests and use them to improve our build environment
Date Thu, 21 Apr 2016 23:21:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-15651:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: master
     Release Note: 
To find recent set of flakies, run the script added by this patch. Run it to get usage information
passing -h:

$ ./dev-support/report-flakies.py -h

If you get the below:

$ python ./dev-support/report-flakies.py
Traceback (most recent call last):
  File "./dev-support/report-flakies.py", line 25, in <module>
    import requests
ImportError: No module named requests

... install the requests module:

$ sudo pip install requests

           Status: Resolved  (was: Patch Available)

Pushed to master branch. Nice script [~appy] (thanks for review [~dimaspivak])

> Track our flaky tests and use them to improve our build environment
> -------------------------------------------------------------------
>                 Key: HBASE-15651
>                 URL: https://issues.apache.org/jira/browse/HBASE-15651
>             Project: HBase
>          Issue Type: Task
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: master
>         Attachments: HBASE-15651-master-v2.patch, HBASE-15651-master-v3.patch, HBASE-15651-master-v4.patch,
HBASE-15651-master.patch, flakies.py, hbase-personality-master.patch
> So i have written this simple script (attached) which looks at history of the [post commit
build|https://builds.apache.org/view/All/job/HBase-Trunk_matrix] and outputs a list of flaky
tests with some numbers.
> Next steps:
> 1. Setup a jenkins job (say *find-flaky-tests*) to run this script daily. We can either
directly pull these results into other jobs using curl on this job's artifacts, or commit
the list of flaky test to repo (idk if it's possible to commit something from jenkins job).
> We'll collect results from both *post-commit* job (to add new flakies) and *flaky-tests*
job (to delete tests which are no more flaky).
> 2. Change *pre-commit* and *post-commit* jobs to ignore these tests using --exclude maven
flag. Someone familiar with yetus might be able to do it easily.
> 3. Setup a new job (say *flaky-tests*) to run only these flaky tests.

This message was sent by Atlassian JIRA

View raw message