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: 
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 haosdent commented on the issue:
https://github.com/apache/mesos/pull/165
Hi, @dcaba Since Mesos have used Apache CI to perform testings instead of
travis ci, could refer to https://issues.apache.org/jira/browse/MESOS-5655 for
the details. And thx @jfarrell, he just
Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
Hi,
a bit surprised travis integration is still enabled (so all PRs have red
crosses)... let me know if you want me to resolve the conflicts to integrate
this (in addition to a basic travis
Github user janisz commented on the issue:
https://github.com/apache/mesos/pull/165
+1 for merge. Can someone shepherd it or disable Travis and wire ASF
Jenkins instead?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user janisz commented on the issue:
https://github.com/apache/mesos/pull/165
I agree with @dcaba if Travis is enabled then it should at least run style
check (whole compile is good too).
> But I think we give up travis ci long time ago?
Why it's still enabled?
---
If
Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
BTW,
I've just remembered a benefit of keeping this active (that will not
affect too much that decision); Travis will run the compilation / ci task not
only when you raise a PR against the
Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
Hi @kaysoky , @haosdent !
thanks so much for your comments. Yep, I see this is not new for the
project, and I was missing a lot of context when I initiated this PR. So now we
have two
Github user haosdent commented on the issue:
https://github.com/apache/mesos/pull/165
Some experience to make it faster as well.
https://reviews.apache.org/r/39257/diff/1#index_header (`-
CXXFLAGS=-gsplit-dwarf`)
But I think we give up travis ci long time ago? Refer to
Github user kaysoky commented on the issue:
https://github.com/apache/mesos/pull/165
You can see [on the ASF Mesos
CI](https://builds.apache.org/job/Mesos/buildTimeTrend) that successful builds
typically takes 60-90 minutes. However, this is for `make distcheck`.
A `make
Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
The build times out after 50 minutes (maximum job length the free version
of travis allows)... I'm afraid we cannot afford executing all the tests in
Travis (last one that initiates is
11 matches
Mail list logo
