[RTEMS Project] #4642: RSB: log.py tends removes relevant error messages

RTEMS trac trac at rtems.org
Wed Jun 8 09:24:15 UTC 2022


#4642: RSB: log.py tends removes relevant error messages
----------------------------+---------------------
 Reporter:  Frank Kuehndel  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:  6.1
Component:  tool/rsb        |     Version:  6
 Severity:  minor           |  Resolution:
 Keywords:                  |  Blocked By:
 Blocking:                  |
----------------------------+---------------------

Comment (by Frank Kuehndel):

 I opened this ticked because I wasted a lot of time looking into the error
 reports and not understanding that the real error is not shown there at
 all. With this ticket, I would like to prevent others to drop into the
 same pit I did fall in.

 An error message like

     `See error report: rsb-report-arm-rtems6-gcc-0f001dd-newlib-
 64b2081-x86_64-linux-gnu-1.txt`

 strongly suggests that the error can be found in the report. This is the
 more confusing when the log close to the end contains something like
 `make: *** [Makefile:965: all] Error 2`. Yet, it turns out that when the
 number of jobs is greater than 1, the "real" error message appears so
 early that it is not in this report. (The real error message appears
 typically just before it says `make: [...] Error 1` - but this may depend
 on the used `make` tool).

     1. "Increasing the log size" does not help as the errors appears a lot
 of lines before the output ends.
     2. "Remove the log tail on error." Keeping the whole log would help.
 Yet, these files are very very large and the current `log.py`
 implementation keeps everything in memory.
     3. "Do nothing and close this ticket?" You can certainly close this
 ticks, as it is not a hard bug. Yet, many stupid users like me will end up
 looking uselessly into the report, instead of identifying the error and
 providing a patch. But nonetheless, just closing this ticket is certainly
 valid.

 As a forth solution I would suggest to print a different text or some text
 below (esp. when the "jobs > 1"), indicating that the error cause in some
 cases can only be spotted in the full log generated by the `-log <log-
 file>` option.

--
Ticket URL: <http://devel.rtems.org/ticket/4642#comment:3>
RTEMS Project <http://www.rtems.org/>
RTEMS Project


More information about the bugs mailing list