| Summary: | LSB 4.1: glib_threads error | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Xiaofeng Yan <Xiaofeng.yan> |
| Component: | core | Assignee: | Xiaofeng Yan <Xiaofeng.yan> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | liang.li2, liangliang.wang, meta.mr.watcher, meta.watcher, sgw, yi.zhao |
| Version: | 1.0-alpha | ||
| Target Milestone: | 1.1 M3 | ||
| Hardware: | mpc8315e-rdb | ||
| OS: | ppc | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
I record this bug and fix it on 1.1 Known problem http://bugs.linuxbase.org/show_bug.cgi?id=3253 (In reply to comment #2) > Known problem > http://bugs.linuxbase.org/show_bug.cgi?id=3253 Known problem http://bugs.linuxbase.org/show_bug.cgi?id=3042 Known problem This bug could happen occasionally, hardware could cause "Child process was terminated by signal 6" because of the limitation of hardware from mpc8315e. if this bug happen when running lsb suite in your side. You can run test.c from http://bugs.linuxbase.org/show_bug.cgi?id=3042 manually. if the result is no problem, then this test item should pass lsb test. With 1.1 M3 build on mpc8315e-rdb, this issue doesn't happen. |
/glib-t2c/tests/glib_threads/glib_threads 36 unresolved Message from the test: Target interface(s): g_static_rw_lock_reader_trylock -------- Checked requirement: {g_static_rw_lock_reader_trylock.01.02} Child process was terminated by signal 6. Abnormal child process termination. errno: 22.