[ 
https://issues.apache.org/jira/browse/HBASE-18540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118915#comment-16118915
 ] 

Jonathan Hsieh edited comment on HBASE-18540 at 8/8/17 7:45 PM:
----------------------------------------------------------------

I use this script on my lappy.  Making it job sounds like it could be useful.

edit: removing private repo link and adding code instead

{code}
#!/bin/bash

CMD="$@"
N=${N:-5}
echo "N = $N"
for i in `seq $N`
do
  $CMD
  RET=$?
  if [ $RET != 0 ]; then
    echo "Failed on iteration $i"
    exit $RET
  fi
done
echo "Succeeded $i iterations"
{code}


was (Author: jmhsieh):
I use this script on my lappy.  Making it job sounds like it could be useful.

edt: removing private repo link and adding code instead

{code}
#!/bin/bash

CMD="$@"
N=${N:-5}
echo "N = $N"
for i in `seq $N`
do
  $CMD
  RET=$?
  if [ $RET != 0 ]; then
    echo "Failed on iteration $i"
    exit $RET
  fi
done
echo "Succeeded $i iterations"
{code}

> Ad-hoc job for checking if a test is flaky
> ------------------------------------------
>
>                 Key: HBASE-18540
>                 URL: https://issues.apache.org/jira/browse/HBASE-18540
>             Project: HBase
>          Issue Type: New Feature
>          Components: test
>            Reporter: Sean Busbey
>
> It would be great if we had an ad-hoc job that could run a given test a bunch 
> of times and tell me if it is flaky.
> I'm trying to evaluate the state of our new nightly jobs, and I'm not sure if 
> hte failures I'm seeing are a) things I need to get fixed soon, b) things 
> that are flaky but previously unrecognized, c) things that are flaky but 
> missed because our current flaky list is only based on the behavior of the 
> master branch.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to