From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Runtime test issues
Date: Wed, 13 Feb 2019 22:25:33 +0100 [thread overview]
Message-ID: <20190213222533.35cac79e@windsurf> (raw)
Hello,
Fran?ois, Ricardo, Yann: you are in Cc because some of the runtime test
cases you added have some issues.
Fran?ois, the following tests are failing:
- tests.package.test_perl_dbd_mysql.TestPerlDBDmysql
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295305
- tests.package.test_prosody.TestProsodyLuajit
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295315
- tests.package.test_prosody.TestProsodyLua51
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295314
Ricardo, the following test is failing:
- tests.download.test_git.TestGitRefs
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295269
Yann, the following tests are failing:
- tests.init.test_systemd.TestInitSystemSystemdRoFull
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295290
- tests.init.test_systemd.TestInitSystemSystemdRwFull
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295293
- tests.init.test_systemd.TestInitSystemSystemdRoNetworkd
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295292
- tests.init.test_systemd.TestInitSystemSystemdRwNetworkd
https://gitlab.com/buildroot.org/buildroot/-/jobs/158295295
Could you have a look at those test failures ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2019-02-13 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 21:25 Thomas Petazzoni [this message]
2019-02-18 2:34 ` [Buildroot] Runtime test issues Ricardo Martincoski
2019-02-18 18:02 ` François Perrad
2019-02-22 20:46 ` Thomas Petazzoni
2019-02-26 3:07 ` Ricardo Martincoski
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=20190213222533.35cac79e@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.