From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Various runtime test failures on Gitlab CI
Date: Sat, 10 Aug 2019 15:52:16 +0200 [thread overview]
Message-ID: <20190810135216.GI21314@scaer> (raw)
In-Reply-To: <20190810151945.5ed664ea@windsurf.home>
Thomas, All,
On 2019-08-10 15:19 +0200, Thomas Petazzoni spake thusly:
> The last Gitlab CI pipeline on master
> (https://gitlab.com/buildroot.org/buildroot/pipelines/75533041/failures)
> shows a number of failures in our runtime tests.
[--SNIP--]
> - For tests.init.test_systemd.TestInitSystemSystemdRwFull, we're
> getting:
>
> Traceback (most recent call last):
> File "/builds/buildroot.org/buildroot/support/testing/tests/init/test_systemd.py", line 157, in test_run
> self.start_emulator("ext2", "zImage", "vexpress-v2p-ca9")
> File "/builds/buildroot.org/buildroot/support/testing/tests/init/base.py", line 38, in start_emulator
> self.emulator.login()
> File "/builds/buildroot.org/buildroot/support/testing/infra/emulator.py", line 92, in login
> raise SystemError("System does not boot")
> SystemError: System does not boot
This one works OK here:
$ ./support/testing/run-tests -o $(pwd)/runtests -k
tests.init.test_systemd.TestInitSystemSystemdRwFull
15:25:25 TestInitSystemSystemdRwFull Starting
15:25:26 TestInitSystemSystemdRwFull Building
15:37:55 TestInitSystemSystemdRwFull Building done
15:38:34 TestInitSystemSystemdRwFull Cleaning up
.
----------------------------------------------------------------------
Ran 1 test in 788.838s
OK
Excerpt of the run log:
10009000.uart: ttyAMA0 at MMIO 0x10009000 (irq = 38, base_baud = 0) is a PL011 rev1
console [ttyAMA0] enabled
[...]
[ ***] (2 of 2) A start job is running for /dev/ttyAMA0 (16s / 1min 31s)
[...]
[ OK ] Found device /dev/ttyAMA0.
[ OK ] Started Serial Getty on ttyAMA0.
while the one on gitlab fails to find the serial:
10009000.uart: ttyAMA0 at MMIO 0x10009000 (irq = 38, base_baud = 0) is a PL011 rev1
console [ttyAMA0] enabled
[...]
[ **] (1 of 2) A start job is running for /dev/ttyAMA0 (1min 28s / 1min 30s)
[...]
[ TIME ] Timed out waiting for device /dev/ttyAMA0.
[DEPEND] Dependency failed for Serial Getty on ttyAMA0.
So, it looks like on my machine, it took abouts 16s for the ttyAMA0
systemd slice to be up (wft? 16s?), while on the gitlab-ci it was not
found...
I'll investigate what makes it appear so late...
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-08-10 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 13:19 [Buildroot] Various runtime test failures on Gitlab CI Thomas Petazzoni
2019-08-10 13:52 ` Yann E. MORIN [this message]
2019-08-10 17:01 ` Yann E. MORIN
2019-08-10 17:28 ` Yann E. MORIN
2019-08-10 22:44 ` 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=20190810135216.GI21314@scaer \
--to=yann.morin.1998@free.fr \
--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.