reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhruv Mahajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1243) Fix StreamingRemoteManagerTest tests which get stuck in AppVeyor
Date Tue, 03 May 2016 20:42:12 GMT

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

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

[~shulmanb] [~markus.weimer] [~afchung90] the lines above should not be the problem. These
observers are registered with corresponding {{StreamingRemoteManager}}s which in turn pass
them over to {{ObserverContainer}} which in turn are passed on to {{StreamingTransportServer}}
to process incoming messages on streams. Hence, note that these observers are not universal
observers but used only for messages assigned to connections created via that RemoteManager
only. Hence, it cannot be the issue here.

I will try to investigate more.

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

Mime
View raw message