Github user haosdent commented on the issue:
https://github.com/apache/mesos/pull/165
yah, actually apache jenkins have integrated with github. Could provide
build status via this badge icons.
Build status: ![](https://builds.apache.org/job/Mesos-Buildbot/badge/icon)
GitHub user aaronjwood opened a pull request:
https://github.com/apache/mesos/pull/205
Clarify existence of FrameworkID in SUBSCRIBE calls.
Wanted to clarify how `FrameworkID` should or shouldn't be set in
`SUBSCRIBE` calls. Spoke with Anand about this earlier today when I was
Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
Great. Thanks for the update; this parallel CI job in travis (this PR was
bringing) was not adding too much benefits (just the nice github <-> travis
integration, that can show green ticks or red
Github user dcaba closed the pull request at:
https://github.com/apache/mesos/pull/165
---
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
+1 (binding)
Since the perf issue I reported earlier doesn't seem to be a blocker.
On Fri, Mar 3, 2017 at 12:14 AM, Alex Rukletsov wrote:
> Was this perf issue introduced by one of the fixes included in 1.1.1-rc2?
> If not, I would suggest we vote for 1.1.1-rc2 and back
+1 (binding)
Since the perf and flaky test that I reported earlier doesn't seem to be
blockers.
On Fri, Mar 3, 2017 at 4:01 PM, Adam Bordelon wrote:
> I haven't heard any -1's so I'm going to go ahead and vote myself, from a
> DC/OS perspective:
>
> +1 (binding)
>
> I ran
I haven't heard any -1's so I'm going to go ahead and vote myself, from a
DC/OS perspective:
+1 (binding)
I ran 1.2.0-rc2 through the DC/OS integration tests on top of the
1.9.0-rc1, which covers many Mesos features and tests multiple frameworks.
See CI results of