12141 2017-09-29 15:59:21 +0000 Pseudo: Annotate error messages 2026-10-27 08:22:16 +0000 1 1 6 Yocto Project Subprojects Pseudo pseudo unspecified x86 Multiple RESOLVED FIXED Medium+ enhancement 6.1 M4 1 juro.bystricky frezidok1 frezidok1 mark.hatle randy.macleod richard.purdie seebs yp.pseudo.watcher yp.watcher --- --- Don't know oldest_to_newest 77232 0 juro.bystricky 2017-09-29 15:59:21 +0000 pseudo can be quite verbose. I have encountered pseudo.log files of more than 4GB. It can be difficult to find meaningful error messages drowned in tons of info/debug messages. It would be very useful if all error messages were prefixed with "ERROR:". Ideal error msg would look something like: ERROR: [component] msg Also similar annotation for other messages "INFO:" "DEBUG:" would make sorting through the pseudo.log easier. 78065 1 richard.purdie 2017-11-08 16:44:32 +0000 Being able to identify real pseudo issues from noise might help us track down some of the occasional permissions errors so this could help with that. 78077 2 seebs 2017-11-08 18:34:23 +0000 It might make sense to add a "severity" to messages. Right now categorization is by topic of thing, but "do I need to know" is a sort of separate category. 96886 3 randy.macleod 2023-10-24 14:24:37 +0000 Bulk move from 4.99 or 0.00 to 5.99 105562 4 frezidok1 2026-05-23 19:13:45 +0000 Hi everyone. I want to start working on this. Does anyone have any tips before I start in addition to what was said earlier? Maybe something's changed since 2017? 105568 5 randy.macleod 2026-05-25 11:46:46 +0000 Thanks Dmitry, Other than, start by doing something simple and sending a patch to feedback, I don't have any tips. I've CCed Mark Hatle who might be able to give you more guidance. 105570 6 mark.hatle 2026-05-25 20:25:13 +0000 As Randy said, just start suggesting logging changes. There are already some categories of information to the pseudo messages, but you'll need to understand the log format and where the messages are. (Many errors/logs might be in generated code, so the code generator is one place that will require modifications.) 106808 7 frezidok1 2026-09-11 07:26:00 +0000 Solution is included to master-next branch. 106822 8 randy.macleod 2026-09-11 20:52:31 +0000 Hi Dmitry, Not all commits to master-next make it into master for oe-core. There will be a patch review meeting on Monday that will include your commit if there are no issues found by the YP autobuilder testsuite. If there are no objections, then the commit will be pushed to master. When that happens, can you add a commit link here and resolve the issue again please ? I'm not sure if you commit was sent to yocto-patch to get into pseudo or somewhere else so when the time is right please explain. The bug is of course only considered resolved once the pseudo code in oe-core has the fix. Thanks for your work on pseudo / Yocto ! 106823 9 frezidok1 2026-09-11 22:01:20 +0000 Sorry, seems like I misinterpreted master-next’s meaning. I’ve sent my patches to yocto-patches, Mark included them in his series and pushed to master-next, so I decided that it had passed all review stages. Thank you for a clear explanation! 106863 10 randy.macleod 2026-09-17 14:43:07 +0000 Moved to In progress review. 107188 11 frezidok1 2026-10-27 08:22:16 +0000 Change status to resolved https://git.yoctoproject.org/pseudo/commit/?id=2afaba574cdece055a2dd8a4d6ccf455ec91c074