| Summary: | Pseudo: Annotate error messages | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Pseudo | Reporter: | Juro Bystricky <juro.bystricky> |
| Component: | pseudo | Assignee: | Dmitry Sakhonchik <frezidok1> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | frezidok1, mark.hatle, randy.macleod, richard.purdie, seebs, yp.pseudo.watcher, yp.watcher |
| Version: | unspecified | ||
| Target Milestone: | 6.1 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Juro Bystricky
2017-09-29 15:59:21 UTC
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. 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. Bulk move from 4.99 or 0.00 to 5.99 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? 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. 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.) Solution is included to master-next branch. 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 ! 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! Moved to In progress review. Change status to resolved https://git.yoctoproject.org/pseudo/commit/?id=2afaba574cdece055a2dd8a4d6ccf455ec91c074 |