All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/5] support/testing: core testing infrastructure
Date: Sun, 7 May 2017 23:38:35 +0200	[thread overview]
Message-ID: <20170507233835.2afdeb9e@free-electrons.com> (raw)
In-Reply-To: <dd7ec6aa-0778-8e92-b031-cbc82c982005@lucaceresoli.net>

Hello,

On Sun, 7 May 2017 23:07:31 +0200, Luca Ceresoli wrote:

> Things that I already commented about and for which I plan to send patches:
> - remove smart_open
> - document code
> - better reporting

Great!

> > +ARTIFACTS_URL = "http://autobuild.buildroot.net/artefacts/"  
> 
> Since you renamed artefacts to artifacts, it's probably good to rename
> in the URL too (and update the server). Sure it's a minor nit, but since
> it's an URL that should stay available for long, better having it fixed
> as soon as possible.

Correct, I'll fix that up.


> > +            qemu_cmd += ["-kernel", kernel]  
> 
> I'm OK with the "builtin" logic, but I really dislike it being
> hard-coded in Emulator.boot(). It's acceptable for the moment since we
> have only very few builtin kernels. Should we add more in the future, I
> think we should at least have a sort of "database" of builtin kernels,
> perhaps in the form of an associative array.

Fully agreed. What we have now is OK for a few kernel/qemu setups, but
clearly does not scale, and will have to be improved.

> Stylish note: I would put the one-letter form before the long form. This
> is not only my personal taste, but also what the manpages usually do,
> and what Python does with the automatically-added -h/--help parameter:

Indeed. Patch welcome! :-)

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-05-07 21:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 20:36 [Buildroot] [PATCH v3 0/5] Runtime testing infrastructure Thomas Petazzoni
2017-03-20 20:36 ` [Buildroot] [PATCH v3 1/5] support/testing: core " Thomas Petazzoni
2017-03-22  8:11   ` Thomas De Schampheleire
2017-03-23  3:02   ` Ricardo Martincoski
2017-03-23  8:07     ` Thomas Petazzoni
2017-03-24  2:19       ` Ricardo Martincoski
2017-03-26 21:54   ` Luca Ceresoli
2017-05-07 21:07   ` Luca Ceresoli
2017-05-07 21:38     ` Thomas Petazzoni [this message]
2017-03-20 20:36 ` [Buildroot] [PATCH v3 2/5] support/testing: add core tests Thomas Petazzoni
2017-03-22  8:17   ` Thomas De Schampheleire
2017-03-22  8:25     ` Thomas Petazzoni
2017-03-22  8:35       ` Thomas De Schampheleire
2017-03-20 20:36 ` [Buildroot] [PATCH v3 3/5] support/testing: add fs tests Thomas Petazzoni
2017-05-07 20:55   ` Luca Ceresoli
2017-03-20 20:36 ` [Buildroot] [PATCH v3 4/5] support/testing: add package tests Thomas Petazzoni
2017-03-22  8:26   ` Thomas De Schampheleire
2017-03-22 13:08     ` Thomas Petazzoni
2017-03-20 20:36 ` [Buildroot] [PATCH v3 5/5] support/testing: add toolchain tests Thomas Petazzoni
2017-03-26 21:53   ` Luca Ceresoli
2017-03-22  8:30 ` [Buildroot] [PATCH v3 0/5] Runtime testing infrastructure Thomas De Schampheleire
2017-05-07 20:09 ` Thomas Petazzoni
2017-05-07 20:41   ` Luca Ceresoli
2017-05-07 21:10     ` Thomas Petazzoni

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=20170507233835.2afdeb9e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.