On Thu, Jun 1, 2017 at 2:22 PM, Benjamin Mahler wrote:
> If I understood correctly, the proposal is to not kill the tasks for
> non-partition aware frameworks? That seems like a pretty big change for
> frameworks that are not partition aware and expect the old killing
>
+1 (binding)
Looks like ExamplesTest.DynamicReservationFramework is flaky, unfortunately
wasn't able to get the logs for a failed run.
On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler wrote:
> Not a blocker, but noticed the parallel test runner isn't bundled in the
>
Hi Ben,
The argument for changing the semantics is that correct frameworks
should _always_ have accounted for the possibility that TASK_LOST
tasks would go back to running (due to the non-strict registry
semantics). The proposed change would just increase the probability of
this behavior
If I understood correctly, the proposal is to not kill the tasks for
non-partition aware frameworks? That seems like a pretty big change for
frameworks that are not partition aware and expect the old killing
semantics.
It seems like we should just directly fix the issue, do you have a sense of
Not a blocker, but noticed the parallel test runner isn't bundled in the
release, if you configure with '--enable-parallel-test-execution':
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
--sequential=*ROOT_* ./stout-tests
/bin/sh:
+Kevin
On Wed, May 31, 2017 at 3:31 PM, Brad wrote:
> Hi all,
>
> I'm interested in the container attach and exec feature added in version
> 1.2.0.
>
> I'm using the LAUNCH_NESTED_CONTAINER_SESSION and ATTACH_CONTAINER_INPUT
> calls on the operator API to launch an
This is great!
I have created a channel for India specific users. Please feel free to join.
--
Subodh Pachghare
Skype ID – subodh.pachghare
Website – www.thesubodh.com
On 01/06/17, 7:07 AM, "Kota UENISHI" wrote:
> If you want, you can create a
7 matches
Mail list logo