Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.0.2.
This is a bug fix release.
The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2-rc2
I can't remember now what the issue was with ubuntu-us1 and untuntu-6. I
can remove the labels and see if things continue to work ok.
Are all `Hadoop` nodes now tagged with `docker` as well?
On Mon, Oct 31, 2016 at 12:23 PM, Daniel Takamori wrote:
> Greetings from the Infra
Greetings from the Infra Team,
We've noticed that some subset of your builds use the label:
"(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)"; recently we've completed
puppetizing the build nodes so they should all match. Are there problems with
ubuntu-us1 and ubuntu-6 that haven't been
>From the log:
I1031 13:57:54.254748 29433 sched.cpp:820] Sending SUBSCRIBE call to
master@172.17.0.2:34385
I1031 13:58:18.482736 29433 sched.cpp:853] Will retry registration in
3.204867476secs if necessary
Looks like this VM experienced a lag.
On 31 October 2016 at 15:04, Apache Jenkins Server
We've recently discovered a bug that may lead to a task being transitioned
from killing to running state. More information about it in MESOS-6457 [1].
We plan to fix it in 1.2.0 and will backport it to all supported versions.
[1] https://issues.apache.org/jira/browse/MESOS-6457
I spent a little while looking into this. The
"PersistentVolumeEndpointsTest.OfferCreateThenEndpointRemove" test
fails on the following expectations:
https://github.com/apache/mesos/blob/1e57459b7d3f571bdf18fec29b070e78ce719319/src/tests/persistent_volume_endpoints_tests.cpp#L1562
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.1.0.
1.1.0 includes the following:
* [MESOS-2449] - **Experimental** support for launching a group of tasks
via a new `LAUNCH_GROUP`
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/174
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rukletsov commented on a diff in the pull request:
https://github.com/apache/mesos/pull/174#discussion_r85733844
--- Diff: docs/contributors.yaml ---
@@ -597,3 +597,12 @@
- xingz...@cn.ibm.com
jira_user: dongdong
reviewboard_user: dongdong
+
Github user rukletsov commented on a diff in the pull request:
https://github.com/apache/mesos/pull/174#discussion_r85733901
--- Diff: docs/contributors.yaml ---
@@ -597,3 +597,12 @@
- xingz...@cn.ibm.com
jira_user: dongdong
reviewboard_user: dongdong
+
Folks,
I observe a lot of flaky tests in Apache Jenkins. They seem rather random
and not tied to particular machines (saw failures on H1 and on H2).
Moreover, there are no tickets for them and I haven't seen any of those
failures in our internal CI.
Does anyone have an idea about any recent
11 matches
Mail list logo