From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [next/testing Lua modules 01/11] luarocks: add generation of test
Date: Thu, 28 Mar 2019 18:22:21 +0100 [thread overview]
Message-ID: <20190328182221.0c60b659@windsurf> (raw)
In-Reply-To: <CAB0FRstu3uefmO9dvqMb=-GiAUEdm78i-ZfKX4Ho-qChH64nUg@mail.gmail.com>
On Thu, 28 Mar 2019 18:13:05 +0100
Fran?ois Perrad <francois.perrad@gadz.org> wrote:
> > Is this expected ?
> >
>
> Yes, more or less.
>
> The lua ecosystem has no common policy about naming, etc...
> So, a generated stuff sometime needs a manual editing.
So for lpeg you really a special .module_test() call ?
Why is the "rings" test case not matching the output of "make
rings-upgrade" ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-28 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 15:43 [Buildroot] [next/testing Lua modules 01/11] luarocks: add generation of test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 02/11] support/testing: add lpeg test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 03/11] support/testing: add lsqlite3 test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 04/11] support/testing: add lua-curl test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 05/11] support/testing: add lua-utf8 test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 06/11] support/testing: add luaexpat test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 07/11] support/testing: add luafilesystem test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 08/11] support/testing: add luaossl test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 09/11] support/testing: add luasec test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 10/11] support/testing: add luasocket test Francois Perrad
2019-02-19 15:43 ` [Buildroot] [next/testing Lua modules 11/11] support/testing: add rings test Francois Perrad
2019-03-28 16:22 ` [Buildroot] [next/testing Lua modules 01/11] luarocks: add generation of test Thomas Petazzoni
2019-03-28 17:13 ` François Perrad
2019-03-28 17:22 ` Thomas Petazzoni [this message]
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=20190328182221.0c60b659@windsurf \
--to=thomas.petazzoni@bootlin.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.