+1 (binding)
make check passed on Ubuntu 16.04
-anand
On Tue, Nov 14, 2017 at 2:49 PM, Kapil Arya wrote:
> +1 (binding)
>
> Mesosphere-internal CI with CentOS 6/7, Debian 8, Fedora 23, and Ubuntu
> 1[467].04.
>
> On Mon, Nov 13, 2017 at 7:14 PM, Vinod Kone
On 11/15/2017 12:18 AM, Kapil Arya wrote:
On Tue, Nov 14, 2017 at 6:05 PM, Adam Cécile > wrote:
Hi,
It's usually considered as being a bad practise to put the Debian
packaging itself into the upstream tree because it conflicts
On Tue, Nov 14, 2017 at 6:05 PM, Adam Cécile wrote:
> Hi,
>
> It's usually considered as being a bad practise to put the Debian
> packaging itself into the upstream tree because it conflicts with the
> "real" packaging if it gets uploaded to Debian.
> But that's probably
Hi,
It's usually considered as being a bad practise to put the Debian
packaging itself into the upstream tree because it conflicts with the
"real" packaging if it gets uploaded to Debian.
But that's probably something we can figure out easily (maybe use
another folder name and add hacky step
That will be awesome. We have ARM Jenkins agent so we can prepare packages
for ARM too.
wt., 14.11.2017, 23:56 użytkownik Kapil Arya napisał:
> Hi Adam,
>
> I am wondering if you would have some time to bring your debian packaging
> into Mesos source tree. We can then use
Hi Adam,
I am wondering if you would have some time to bring your debian packaging
into Mesos source tree. We can then use the ASF Jenkins CI to build and
publish packages to bintray just like we started doing for CentOS 6/7? This
will also allow the community to more actively participate in
+1 (binding)
Mesosphere-internal CI with CentOS 6/7, Debian 8, Fedora 23, and Ubuntu
1[467].04.
On Mon, Nov 13, 2017 at 7:14 PM, Vinod Kone wrote:
> +1 (binding)
>
> Tested on ASF CI. Couple red failure builds were due to known flaky tests,
> one of which is already
That seems weird then. A new agent coming up on a new ip and host,
shouldn't affect other agents running on different hosts. Can you share
master logs that surface the issue?
On Tue, Nov 14, 2017 at 12:51 PM, Dan Leary wrote:
> Just one mesos-master (no zookeeper) with
Just one mesos-master (no zookeeper) with --ip=127.0.0.1
--hostname=localhost.
In /etc/hosts are
127.1.1.1agent1
127.1.1.2agent2
etc. and mesos-agent gets passed --ip=127.1.1.1 --hostname=agent1 etc.
On Tue, Nov 14, 2017 at 3:41 PM, Vinod Kone wrote:
>
So I have a bespoke framework that runs under 1.4.0 using the v1 HTTP API,
custom executor, checkpointing disabled.
When the framework is running happily and a new agent is added to the
cluster all the existing executors immediately get terminated.
The scheduler is told of the lost executors and
10 matches
Mail list logo