All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] lttng-tools: improve ptest and test suite
Date: Fri, 05 Apr 2019 18:01:43 +0100	[thread overview]
Message-ID: <134736ff908c53c1cc916afb737da7ce367fbd2b.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190404214743.9827-1-jonathan.rajotte-julien@efficios.com>

On Thu, 2019-04-04 at 21:47 +0000, Jonathan Rajotte wrote:
> Multiple patches are to be applied to improve the current ptest
> suite.
> 
> 0001-Fix-tests-link-libpause_consumer-on-liblttng-ctl.patch
> 0002-Fix-test-skip-test_getcpu_override-on-single-thread-.patch
> 0003-Fix-test-unit-the-tree-origin-can-be-a-symlink-itsel.patch
> 0006-Tests-check-for-lttng-modules-presence.patch
> 
> All deal with problem in the test suite. Most of these are already
> accepted upstream and will be removed on the next recipe update.

Just wanted to say thanks for working on this. Its made a significant
improvement to the overall ptest execution time without the timeout and
the test results, both of which are hugely useful to us.

I think there was one failure in last night's test of these patches
which is great compared to where we were! :)

Cheers,

Richard



  parent reply	other threads:[~2019-04-05 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 21:47 [PATCH 1/4] lttng-tools: improve ptest and test suite Jonathan Rajotte
2019-04-04 21:47 ` [PATCH 2/4] lttng-ust: backport musl workaround Jonathan Rajotte
2019-04-04 21:47 ` [PATCH 3/4] lttng-ust: lttng-ust works fine on musl no need to remove it Jonathan Rajotte
2019-04-04 21:47 ` [PATCH 4/4] lttng-tools: lttng-tools " Jonathan Rajotte
2019-04-05 16:14 ` [PATCH 1/4] lttng-tools: improve ptest and test suite Khem Raj
2019-04-05 17:01 ` richard.purdie [this message]
2019-04-23  9:25 ` Burton, Ross
2019-04-23 12:31   ` Jonathan Rajotte-Julien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=134736ff908c53c1cc916afb737da7ce367fbd2b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.