Description
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:
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
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).