| Summary: | do_package_setscene failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Matthew McClintock <msm-oss> | ||||
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Low | CC: | msm-oss, poky.bs.watcher, poky.watcher | ||||
| Version: | 1.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
|
Description
Matthew McClintock
2011-11-24 11:27:46 UTC
Created attachment 283 [details]
console out on failure
Is this still happening for you? I don't see this here and to be able to figure anything further out I need the do_package_setscene logs from the xf86bigfontproto temp directory (from its WORKDIR) to see what the failure was. (In reply to comment #2) > Is this still happening for you? I don't see this here and to be able to figure > anything further out I need the do_package_setscene logs from the > xf86bigfontproto temp directory (from its WORKDIR) to see what the failure was. This just happened last night... I've been running 2 builds concurrently for about a week and this is the first I've seen of it... -M Please ignore my "is this still happening" question, I misread the timestamp on the bug. The request for a logfile stands. It would be useful if you could reproduce this against master too given the number of changes in this area that have taken place there. Specific build logs are gone now.... Should'nt bitbake spit out this build failure to the console? It does so for compile/configure/install.... -M (In reply to comment #4) > Please ignore my "is this still happening" question, I misread the timestamp on > the bug. The request for a logfile stands. It would be useful if you could > reproduce this against master too given the number of changes in this area that > have taken place there. I'll let you know if I see it on master... but resources are thin and I don't even remember the last time I built master =( -M "setscene" functions are optional in that if they fail, we'll just build the failed component. We don't really want to scare the user with scary failures with things then magically working which is why the bitbake exit code isn't affected either. So I think its behaving as designed although in this case it likely does mean we've lost the useful logfile :( I'm going to close this since I have no way to fix this based on the current information. If you see it again and get a log file please reopen and we'll see if we can figure out whats going on. |