| Summary: | Ptest log parsing taking hours on the autobuilder | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [QA/Testing] Package Testing (ptest) | Reporter: | Richard Purdie <richard.purdie> | ||||
| Component: | ptest | Assignee: | Richard Purdie <richard.purdie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | High | CC: | akuster808, akuster, randy.macleod | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.1 M3 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | with backport | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Richard Purdie
2019-12-10 13:18:53 UTC
Created attachment 4598 [details]
Log file its trying to parse
This the bluez5 upgrade increased the logs from 5 -> 65 MB and this broke the parser which isn't scaling. would creating a ptest log per package help ? (In reply to comment #3) > would creating a ptest log per package help ? Well, it could but we should just fix the stupid code ;-) Patch on the mailing list and queued in -next |