| Summary: | Tail first failing log in yocto-build email summaries | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Darren Hart <dvhart> |
| Component: | autobuilder | Assignee: | Beth Flanagan <elizabeth.flanagan> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | elizabeth.flanagan, infras.ab.watcher, Infras.watcher, sgw, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.3 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P1)(Done) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2012-02-27 20:22:58 UTC
I'm concerned that if this is targeted for M3 it will get postponed for more urgent release issues. We will also get much less benefit from it if it comes out more than halfway through the release cycle. Any chance this could come in to M2? Moving to M3, delayed by other release work. Moving back to M2. I'm in final testing/implementation. I'll know in an hour if this is complete or not. I have the code for this implemented in the AB. As it's not yocto-ab centric and is a customization, I'll not be pulling this into the main AB repo, except maybe as a note in the README. Marking as resolved. Setting as verified since we already have emails going out and QA doesn't really need to test this. |