OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The flakey test dashboard is broken


thanks Duo!

On Mon, Jul 2, 2018 at 8:45 AM, 张铎(Duo Zhang) <palomino219@xxxxxxxxx> wrote:
> https://issues.apache.org/jira/browse/HBASE-20834
>
> 2018-07-02 21:28 GMT+08:00 Sean Busbey <busbey@xxxxxxxxxx>:
>
>> Please file an HBase JIRA and I'll either chase it down or find
>> someone to. I think that may have been a Cloudera hosted VM.
>>
>> On Mon, Jul 2, 2018 at 8:07 AM, 张铎(Duo Zhang) <palomino219@xxxxxxxxx>
>> wrote:
>> > I do not think this machine is owned by ASF. It is maintained by Appy in
>> > the past.
>> >
>> > 2018-07-02 18:40 GMT+08:00 Ted Yu <yuzhihong@xxxxxxxxx>:
>> >
>> >> Please log an INFRA ticket.
>> >>
>> >> On Mon, Jul 2, 2018 at 3:12 AM, 张铎(Duo Zhang) <palomino219@xxxxxxxxx>
>> >> wrote:
>> >>
>> >> > The console output is
>> >> >
>> >> >
>> >> > + docker run -v
>> >> > > /home/jenkins/jenkins-slave/workspace/HBase-Find-Flaky-Tests:/hbase
>> >> > > --workdir=/hbase hbase-dev-support python
>> dev-support/report-flakies.py
>> >> > > --mvn -v --urls=https://builds.apache.org/job/HBASE-Flaky-Tests/
>> >> > > --max-builds=30 --is-yetus=False --urls=
>> >> > > https://builds.apache.org/job/HBase%20Nightly/job/master/
>> >> --max-builds=6
>> >> > > --is-yetus=True --urls=
>> >> > > https://builds.apache.org/job/HBASE-Flaky-Tests-branch2.0/
>> >> > > --max-builds=30 --is-yetus=False --urls=
>> >> > > https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
>> >> > > --max-builds=6 --is-yetus=True --urls=
>> >> > > http://104.198.223.121:8080/job/HBASE-Flaky-Tests/ --max-builds=30
>> >> > > --is-yetus=False
>> >> > > Traceback (most recent call last):
>> >> > > File "dev-support/report-flakies.py", line 151, in <module>
>> >> > > expanded_urls = expand_multi_config_projects(args)
>> >> > > File "dev-support/report-flakies.py", line 128, in
>> >> > > expand_multi_config_projects
>> >> > > response = requests.get(job_url + "/api/json").json()
>> >> > > File "/usr/lib/python2.7/dist-packages/requests/api.py", line 55,
>> in
>> >> get
>> >> > > return request('get', url, **kwargs)
>> >> > > File "/usr/lib/python2.7/dist-packages/requests/api.py", line 44,
>> in
>> >> > > request
>> >> > > return session.request(method=method, url=url, **kwargs)
>> >> > > File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line
>> >> 455,
>> >> > in
>> >> > > request
>> >> > > resp = self.send(prep, **send_kwargs)
>> >> > > File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line
>> >> 558,
>> >> > in
>> >> > > send
>> >> > > r = adapter.send(request, **kwargs)
>> >> > > File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line
>> >> 378,
>> >> > in
>> >> > > send
>> >> > > raise ConnectionError(e)
>> >> > > requests.exceptions.ConnectionError:
>> >> > > HTTPConnectionPool(host='104.198.223.121', port=8080): Max retries
>> >> > exceeded
>> >> > > with url: /job/HBASE-Flaky-Tests//api/json (Caused by <class
>> >> > > 'socket.error'>: [Errno 111] Connection refused)
>> >> > > Build step 'Execute shell' marked build as failure
>> >> >
>> >> >
>> >> > I think the problem is that, the jenkins instance is broken
>> >> >
>> >> > http://104.198.223.121:8080/job/HBASE-Flaky-Tests/
>> >> >
>> >> > I temporarily removed this url from the build. Does any one know who
>> is
>> >> the
>> >> > maintainer of this machine?
>> >> >
>> >> > Thanks.
>> >> >
>> >>
>>