Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Tue, 3 May 2016 17:17:12 +0000 (UTC)
From: "Dhruv Mahajan (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12948622.1457573890000.99876.1462295832940@Atlassian.JIRA>
In-Reply-To: <JIRA.12948622.1457573890000@Atlassian.JIRA>
References: <JIRA.12948622.1457573890000@Atlassian.JIRA> <JIRA.12948622.1457573890980@arcas>
Subject: [jira] [Commented] (REEF-1243) Fix StreamingRemoteManagerTest tests
 which get stuck in AppVeyor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 May 2016 17:17:15 -0000


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

Dhruv Mahajan commented on REEF-1243:
-------------------------------------

will have a look later this afternoon.

> Fix StreamingRemoteManagerTest tests which get stuck in AppVeyor
> ----------------------------------------------------------------
>
>                 Key: REEF-1243
>                 URL: https://issues.apache.org/jira/browse/REEF-1243
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Dhruv Mahajan
>
> AppVeyor test runs get stuck on tests from {{StreamingRemoteManagerTest}} group:
> * https://ci.appveyor.com/project/ApacheSoftwareFoundation/reef/build/11-master/tests - stuck on {{TestStreamingRegisterObserverByType}}
> * https://ci.appveyor.com/project/ApacheSoftwareFoundation/reef/build/13-master/tests - stuck on {{TestStreamingCommunicationThreeNodesBoth}}
> * https://ci.appveyor.com/project/tcNickolas/reef/build/0.14.0-SNAPSHOT.25-APPVEYOR_EXP/tests - stuck on {{TestStreamingCachedConnection}}
> I can't repro this locally. We need to investigate and fix this.
> To repro this on AppVeyor, one can add their mirror of reef to AppVeyor projects (https://ci.appveyor.com/projects/new after you're logged in with your GitHub account), and then everything pushed to any branch in the mirror gets executed in AppVeyor with the same settings as on main reef. It is possible to limit the scope of tests executed by modifying {{test_script}} section. For example, to run only O.A.R.Tests change it to:
> {noformat}
> test_script:
>   - cd .\lang\cs
>   - cmd: .\packages\xunit.runner.console.2.1.0\tools\xunit.console.exe .\bin\x64\Debug\Org.Apache.REEF.Tests\Org.Apache.REEF.Tests.dll
> {noformat}
> I haven't found a way to access machine on which tests are run directly, only via scripts added to {{appveyor.yml}}.
> This change should also include reverting REEF-1311 (including {{StreamingRemoteManagerTest}} tests to AppVeyor coverage again).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)