You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/07/16 15:52:19 UTC

[GitHub] [flink] azagrebin commented on issue #9105: [FLINK-13241][Yarn/Mesos] Fix Yarn/MesosResourceManager setting managed memory size into wrong configuration instance.

azagrebin commented on issue #9105: [FLINK-13241][Yarn/Mesos] Fix Yarn/MesosResourceManager setting managed memory size into wrong configuration instance.
URL: https://github.com/apache/flink/pull/9105#issuecomment-511876024
 
 
   @xintongsong true, technically the currently adjusted test would have been failed. Only `MesosResourceManager` change seems still to be uncovered.
   
   My question was more about the test coverage of the original effort that did not catch this bug. Basically do we have IT tests to check that the TM containers are created with the correct profile and/or number of slots?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services