From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: benjamin.esquivel@linux.intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository.
Date: Thu, 01 Dec 2016 11:00:41 -0600 [thread overview]
Message-ID: <5685041.Q7lPjqZr2f@mlopezva-mobl2> (raw)
In-Reply-To: <1480611160.13546.2.camel@linux.intel.com>
On Thursday, December 01, 2016 10:52:40 AM Benjamin Esquivel wrote:
> Hi Mariano
>
> On Thu, 2016-12-01 at 09:37 -0600, mariano.lopez@linux.intel.com wrote:
> > From: Mariano Lopez <mariano.lopez@linux.intel.com>
> >
> > This new option allows to commit the result to a git repository,
> > along with the results it will add a metadata file for information
> > of the current selftest run, such as: hostname, machine, distro,
> > distro version, host version, and layers.
> >
> > This implementation will have a branch per different hostname,
> > testing branch, and machine.
> >
> > To use this feature use:
> >
> > oe-selftest <options> --repository <repository_link>
> >
> > [YOCTO #9954]
> I think this version is okay :) have you tested it in an Autobuilder
> task?
Indeed, that is why it took me a bit longer to submit the patch. I
know this won't blow up current master. But Ihaven't used the
option yet, we would need a remote repo and a new autobuilder
buildset.
next prev parent reply other threads:[~2016-12-01 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 15:37 [PATCHv2 0/3] Add communication mechanism for sending test results mariano.lopez
2016-12-01 15:37 ` [PATCHv2 1/3] oeqa/utils/commands.py: Make a copy of variables in get_bb_vars mariano.lopez
2016-12-01 15:37 ` [PATCHv2 2/3] oeqa/utils/metadata.py: Add metadata library mariano.lopez
2016-12-05 9:35 ` Markus Lehtonen
2016-12-01 15:37 ` [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository mariano.lopez
2016-12-01 16:52 ` Benjamin Esquivel
2016-12-01 17:00 ` Mariano Lopez [this message]
2016-12-01 22:44 ` Benjamin Esquivel
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=5685041.Q7lPjqZr2f@mlopezva-mobl2 \
--to=mariano.lopez@linux.intel.com \
--cc=benjamin.esquivel@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox