[
https://issues.apache.org/jira/browse/HBASE-20979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562972#comment-16562972
]
Sean Busbey commented on HBASE-20979:
-------------------------------------
> We do not need to check 200 for other two requests?
We could; it would help make things like transient errors more obvious. but my
only concern thus far has been when the job goes away entirely, since that's
the only failure mode that's happened thus far.
> Flaky test reporting should specify what JSON it needs and handle HTTP errors
> -----------------------------------------------------------------------------
>
> Key: HBASE-20979
> URL: https://issues.apache.org/jira/browse/HBASE-20979
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Minor
> Attachments: HBASE-20979.0.txt
>
>
> Current flaky test report should be including the {{tree=}} parameter in its
> Jenkins API calls (see
> https://support.cloudbees.com/hc/en-us/articles/217911388-Best-Practice-For-Using-Jenkins-REST-API).
> Also should provide some info on failure so that when jobs change or go away
> we don't get blank failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
