reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Chung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1243) Fix StreamingRemoteManagerTest tests which get stuck in AppVeyor
Date Wed, 11 May 2016 16:46:12 GMT

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

Andrew Chung commented on REEF-1243:
------------------------------------

Update: It seems like the cause was due to threadpool starvation by using {{Task.Run}} for
long running threads that block on {{Read}}. After spinning off a dedicated thread with {{Task.Factory.StartNew}}
with {{TaskCreationOptions.LongRunning}}, I was able to get the test to pass without my previous
modification. Will send a PR soon.

> 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.Wake.Tests change it to:
> {noformat}
> test_script:
>   - cmd: cd .\lang\cs
>   - cmd: nuget restore .\.nuget\packages.config -o .\packages
>   - cmd: .\packages\xunit.runner.console.2.1.0\tools\xunit.console.exe .\bin\x64\Debug\Org.Apache.REEF.Wake.Tests\Org.Apache.REEF.Wake.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