[
https://issues.apache.org/jira/browse/ARTEMIS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715530#comment-16715530
]
ASF subversion and git services commented on ARTEMIS-1894:
----------------------------------------------------------
Commit afa0822fd0f8360cb6c43e28f2edd10d4ab5d6f2 in activemq-artemis's branch
refs/heads/1.x from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=afa0822 ]
ARTEMIS-1894 Avoiding apache.org URL on codebase
(cherry picked from commit 1369690f574c2c97d1fa3930260eae5039b703c1)
> NetworkHeathTest hits apache.org (or fails to) as a side effect
> ---------------------------------------------------------------
>
> Key: ARTEMIS-1894
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1894
> Project: ActiveMQ Artemis
> Issue Type: Test
> Affects Versions: 2.6.1, 2.7.0
> Reporter: Robbie Gemmell
> Assignee: clebert suconic
> Priority: Critical
> Fix For: 2.7.0, 2.6.4
>
>
> Looking at some test output from a TravisCI PR test run
> ([https://travis-ci.org/apache/activemq-artemis/builds/385489050)] I noticed
> it complains about socket read timeout against apache.org a couple times
> (plus some localhost failures also).
> It seems that NetworkHealthTest tests hit apache.org (and looking at it,
> presumably the redhat site too) essentially as a side effect while checking
> parsing behaviour for the checker, as they are used for validation as added
> and a warning emitted if they couldnt be. The tests still pass.
> The tests shouldn't hit apache.org at all. Whilst its very low volume
> overall, those servers already have enough real traffic to deal with, and its
> unlikely to make friends for when the infra ban hammers come out to play.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
