> On Mar 22, 2018, at 10:06 AM, Zhitao Li wrote:
>
> In our environment, we run a lot of batch jobs, some of which have tight
> timeline. If any tasks in the job runs longer than x hours, it does not make
> sense to run it anymore.
>
> For instance, a team would
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/275
---
GitHub user joerg84 opened a pull request:
https://github.com/apache/mesos/pull/275
Fix broken link to zookeeper documentation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joerg84/mesos patch-3
Alternatively you can review
In our environment, we run a lot of batch jobs, some of which have tight
timeline. If any tasks in the job runs longer than x hours, it does not
make sense to run it anymore.
For instance, a team would submit a job which builds a weekly index and
repeats every Monday. If the job does not finish
I think such policy would help us discover and act on forgotten disabled
tests. The reason I am reluctant to propose this as an official policy is
because I don't know how to enforce it.
On 21 Mar 2018 6:00 pm, "Vinod Kone" wrote:
> Thanks for doing this Alex! Are you
Seems like there is no agenda item for tomorrow's WG meeting. We will
cancel it at this time.
On Wed, Mar 21, 2018 at 10:30 AM, Gilbert Song wrote:
> Folks,
>
> We are planning for a WG meeting tomorrow at 9 am PST.
>
> Please add any agenda item or topic that you like to