From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] classes/testimage: When image is systemd enable debug log level
Date: Mon, 25 Jul 2016 12:21:22 -0500 [thread overview]
Message-ID: <57964A92.1070204@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZ_jV7BoyhGAn_xjydZMCFsbcdp_5dvaGTgbNy5MDsfqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On 07/15/2016 02:34 PM, Burton, Ross wrote:
> On 12 July 2016 at 22:29, Aníbal Limón <anibal.limon@linux.intel.com> wrote:
>
>> + bootparams = 'systemd.log_level=debug systemd
>> .log_target=console'
>>
>
> The problem with this is that it appears that logger output then goes
> *only* to the console and not the journal or syslog, which breaks selftest
> (and expected behaviour).
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/851
> for example, which goes green if I revert this patch.
>
> If this is the case then it would be great if there was a
> journal-and-console log_target I guess.
I'll review the issue i guess the journal test is failing for something
else but if we change the backend to journalctl systemd starts to fail
with timeout, seems that create a log of I/O writing in the journal
database.
alimon
>
> Ross
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-07-25 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:29 [PATCH 1/3] linux-yocto: Enable debug/printk.scc KERNEL_FEATURE on qemuall machines Aníbal Limón
2016-07-12 21:29 ` [PATCH 2/3] utils/qemurunner.py: QemuRunner.start() add support for specify extra kernel cmdline Aníbal Limón
2016-07-12 21:29 ` [PATCH 3/3] classes/testimage: When image is systemd enable debug log level Aníbal Limón
2016-07-15 19:34 ` Burton, Ross
2016-07-25 17:21 ` Aníbal Limón [this message]
2016-07-25 20:57 ` Aníbal Limón
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=57964A92.1070204@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox