From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Nicolas Carrier <Nicolas.Carrier@orolia.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Raphael Pavlidis <raphael.pavlidis@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v3 1/1] package/shadow: new package
Date: Sat, 10 Dec 2022 09:28:57 +0100 [thread overview]
Message-ID: <20221210082857.GP2855@scaer> (raw)
In-Reply-To: <AS4P251MB0612D4DF753A307318923B9A841C9@AS4P251MB0612.EURP251.PROD.OUTLOOK.COM>
Nicolas, All,
On 2022-12-09 11:07 +0000, Nicolas Carrier spake thusly:
> About the author name, don't bother, I don't mind if you take the
> ownership (read: the blame :D) of the script.
What one can do in this case, is add a co-author tag, like;
Co-authored-by: Nicolas Carrier <Nicolas.Carrier@orolia.com>
[Nicolas.Carrier@orolia.com provided the test case]
Signed-off-by: Raphael Pavlidis <raphael.pavlidis@gmail.com>
> That said, maybe buildroot maintainers would like it to be expanded?
> I don't know the policy for this kind of tests, is it sufficient
> that it demonstrates that the package is able to build something that
> works or is it expected to have something more exhaustive?
It is perfectly fine to have a test case that demonstrates the basics of
the package. This helps prove that there are no missing runtime
dependencies (e.g. for pythn packages), that the basic features do work
as expected, at least in the use-case the submitter is interested in.
If there are more to test, it can be added as time passes (e.g. when we
get a report that something does not work).
We definitely do not want to be able to run the full test-suite of the
package itself; that's not our role.
> Also, there are those:
> self.assertRunOk(f'userdel {username} || true')
> self.assertRunOk(f'groupdel {username} || true')
> Which I had to had, but I never fully understood why they were needed.
assertRunOk() checks that the return code is zero, and drops the output.
So, if self.assertRunOk(f'userdel {username}') fails, then it means that
userdel in the target did fail, so it would be interesting to check why:
output, ret = self.emulator.run(f'userdel {username}')
self.assertEqual(ret, 0, f'Failed with {output!r}')
(I think in fact ythat this is what we should do in assertRunOk())
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-10 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 12:43 [Buildroot] [PATCH v2 1/1] package/shadow: new package Raphael Pavlidis
2022-09-05 10:06 ` Arnout Vandecappelle
2022-09-05 11:51 ` Yann E. MORIN
2022-09-05 12:01 ` Yann E. MORIN
2022-09-11 11:22 ` Raphael Pavlidis
2022-09-11 12:14 ` Yann E. MORIN
2022-09-11 12:55 ` Raphael Pavlidis
2022-09-11 17:57 ` Yann E. MORIN
2022-10-13 16:34 ` [Buildroot] [PATCH v3 " Raphael Pavlidis
2022-12-05 15:48 ` Nicolas Carrier
2022-12-05 21:55 ` Yann E. MORIN
2022-12-06 18:20 ` Raphael Pavlidis
2022-12-08 15:15 ` Nicolas Carrier
2022-12-09 10:24 ` Raphael Pavlidis
2022-12-09 11:07 ` Nicolas Carrier
2022-12-10 8:28 ` Yann E. MORIN [this message]
2022-12-16 9:42 ` Raphael Pavlidis
2022-12-16 14:34 ` Nicolas Carrier
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=20221210082857.GP2855@scaer \
--to=yann.morin.1998@free.fr \
--cc=Nicolas.Carrier@orolia.com \
--cc=buildroot@buildroot.org \
--cc=raphael.pavlidis@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.