Should be resolved now.
On Tue, Sep 6, 2016 at 11:21 AM, Maximilian Michels wrote:
> The testing code for Yarn is very fragile. Also, I'm puzzled why the
> code to test the VCores setting is in the TaskManagerFailure test.
> Running some more tests to fix the issue.
>
> On Tue, Sep 6, 2016 at 7:2
The testing code for Yarn is very fragile. Also, I'm puzzled why the
code to test the VCores setting is in the TaskManagerFailure test.
Running some more tests to fix the issue.
On Tue, Sep 6, 2016 at 7:28 AM, Vijay Srinivasaraghavan
wrote:
> Hi Max,
> I have pulled and tested with the latest mas
Hi Max,
I have pulled and tested with the latest master, but I am still seeing some
issues.
---Test
set:
org.apache.flink.yarn.YARNSessionCapacitySchedulerITCase---
Hi Vijay,
The test fails when a NodeReport with used resources set to null is
retrieved. The test assumes that a TaskManager is always exclusively
running in one Yarn NodeManager which doesn't have to be true as one
NodeManager can host multiple containers. The test only seems to
reliably fail whe
Hi Robert,
Yes, I am consistently seeing the issue. Here is the stack track for the run.
> mvn test integration-test
> -Dtest="YARNSessionCapacitySchedulerITCase#testTaskManagerFailure"
> -Pinclude-yarn-tests -pl flink-yarn-tests -DfailIfNoTests=false
[INFO] Scanning for projects...[INFO]
Hi Vijay,
are you seeing the issues on your local machine, or on Travis?
Are the errors reproducible?
Can you post the full stack trace here?
Regards,
Robert
On Fri, Sep 2, 2016 at 6:24 PM, Vijay Srinivasaraghavan <
vijikar...@yahoo.com> wrote:
> Hello,
>
> I am seeing a "timeout" issue for on
Hello,
I am seeing a "timeout" issue for one of the Yarn test case
(YarnSessionCapacitySchedulerITCase>YarnTestBase.checkClusterEmpty) and noticed
similar references in FLINK-2213 (https://github.com/apache/flink/pull/1588)
I have tested in latest mater code. Is anyone seeing this issue?
RegardsV
