| Summary: | [RFE] Make console.log even more readable remove whole ansi sequences | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Marian Ganisin <mganisin> |
| Component: | lab controller | Assignee: | Bill Peck <bpeck> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.8 | CC: | bpeck, dcallagh, mcsontos, psplicha, rmancy, stl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-07-20 00:38:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
That is a very good idea as the mega-long lines actually "hide" the real cause of installation failures. For a nice example see: http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/06/2552/255267/543816/console.log The implementation should be straightforward. Could we get this fixed any time soon? Beaker 0.9.1 has been released. |
Removal of 'escape characters' doesn't help with reading of console.log too much. It would be much better to remove/replace whole control sequences. For example this dirty sequence of regular expressions makes console.log provided by beaker (with escape characters already removed) much more readable: sed -e 's/??\+//g' -e 's/\[[0-9]\+;\?[0-9]*[AHBKC]\?//g' -e 's/ \{10,\}/\n/g' console.log It could be much easier with 'escape' included, regexp could match exact syntax of sequence. Server-side can handle it.