Sorry, I missed the list in CC.
Em 26/05/2017 04:12, Martin Kletzander escreveu:
And I didn't check the documentation because I
didn't like the fact that coveralls.io wanted _write_ access to my
commit messages and repositories, so I didn't sign up.
I'm afraid I disagree. It requires
Em 31/05/2017 12:38, Daniel P. Berrange escreveu:
On Wed, May 31, 2017 at 12:21:05PM -0300, claudioandre...@gmail.com wrote:
From: Claudio André <claudioandre...@gmail.com>
It is possible to test libvirt using other distros in Travis via Docker;
including (but not limited to) Fedora and
Em 31/05/2017 04:12, Martin Kletzander escreveu:
Without -qq is much worse. We can:
1. collapse as seen above;
2. redirect stdout to /dev/null (I mean, there is no important
information here).
I prefer (and use) #2.
either -qq collapsed or just put it to /dev/null. I don't care which
one,
Em 29/05/2017 08:54, Martin Kletzander escreveu:
On Sun, May 28, 2017 at 11:07:41PM -0300, claudioandre...@gmail.com
wrote:
From: Claudio André <claudioandre...@gmail.com>
'modprobe -c' fails for some reason.
Ahh! Well, it is possible to run modprobe inside Docker if I enable some
o
Sorry, I mean RFC.
Em 30/05/2017 12:28, claudioandre...@gmail.com escreveu:
From: Claudio André <claudioandre...@gmail.com>
Sanitizers are based on compile-time instrumentation. They are available in gcc
and clang for a range of supported operation systems and platforms. More info
at:
Em 26/05/2017 04:12, Martin Kletzander escreveu:
Oh, so it's saved in your profile on the travis website. That makes
sense. I was just wondering where this environment variable gets
defined, that's it. And I didn't check the documentation because I
didn't like the fact that coveralls.io
Em 26/05/2017 04:15, Martin Kletzander escreveu:
On Thu, May 25, 2017 at 07:54:13PM -0300, Claudio André wrote:
The workers available in Travis are really old. That said, I plan to
workaround your finding and propose a patch:
- to build and test libvirt using a more updated distro (using
Em 25/05/2017 03:49, Martin Kletzander escreveu:
On Thu, May 25, 2017 at 01:14:36AM -0300, claudioandre...@gmail.com
wrote:
From: Claudio André <claudioandre...@gmail.com>
It builds the code coverage report and uploads the coverage data to a
web service in order to allow to track lib
Em 25/05/2017 05:21, Daniel P. Berrange escreveu:
On Thu, May 25, 2017 at 01:14:36AM -0300, claudioandre...@gmail.com wrote:
@@ -64,7 +65,8 @@ before_install:
# the custom PATH is just to pick up OS-X homebrew & its harmless on Linux
before_script:
- -
Em 25/05/2017 11:15, Martin Kletzander escreveu:
I need to investigate why this doesn't work, I don't have that file
[...]
Just figured that out. The systems in Travis are just so old that the
automake there doesn't create the test-suite.log =(
The workers available in Travis are really
Below an example of why it is desirable.
Em 25/05/2017 02:19, claudioandre...@gmail.com escreveu:
From: Claudio André <claudioandre...@gmail.com>
Disclosure the content of the 'test-suite.log' file (if available) in case of
failures inside Travis-CI. This is needed to understand what ha
Em 11/05/2017 10:35, Daniel P. Berrange escreveu:
On Thu, May 11, 2017 at 03:30:00PM +0200, Martin Kletzander wrote:
On Tue, Apr 18, 2017 at 02:39:28PM -0300, Claudio André wrote:
Using GitHub libvirt site, it is possible to show Travis's fancy icon of the
current build status. It highlights
Using GitHub libvirt site, it is possible to show Travis's fancy icon of the
current build status. It highlights the QA process.
---
README.md | 12
1 file changed, 12 insertions(+)
create mode 100644 README.md
diff --git a/README.md b/README.md
new file mode 100644
index
Follow up of the recent 'work in progress' announced in "Enable CI build
testing with Travis" mailing message.
Claudio André (1):
Enable Travis CI build status icon
README.md | 12
1 file changed, 12 insertions(+)
create mode 100644 README.md
--
2.11.0
--
libvir-li
14 matches
Mail list logo
