You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/09/27 18:31:00 UTC

[jira] [Assigned] (ARTEMIS-1894) NetworkHeathTest hits apache.org (or fails to) as a side effect

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

clebert suconic reassigned ARTEMIS-1894:
----------------------------------------

         Assignee: clebert suconic
    Fix Version/s: 2.6.4
                   2.7.0

> 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)