1119 2011-05-27 05:01:27 +0000 LSB 4.1: glib_threads error 2011-08-19 01:45:25 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.0-alpha mpc8315e-rdb ppc RESOLVED WONTFIX Medium normal 1.1 M3 1 Xiaofeng.yan Xiaofeng.yan liang.li2 liangliang.wang meta.mr.watcher meta.watcher sgw yi.zhao --- --- --- oldest_to_newest 14042 0 Xiaofeng.yan 2011-05-27 05:01:27 +0000 /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. 14043 1 Xiaofeng.yan 2011-05-27 05:02:09 +0000 I record this bug and fix it on 1.1 15091 2 Xiaofeng.yan 2011-07-28 23:21:27 +0000 Known problem http://bugs.linuxbase.org/show_bug.cgi?id=3253 15092 3 Xiaofeng.yan 2011-07-28 23:46:53 +0000 (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 15098 4 Xiaofeng.yan 2011-07-29 01:16:33 +0000 Known problem 15452 5 Xiaofeng.yan 2011-08-14 21:28:23 +0000 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. 15596 6 yi.zhao 2011-08-19 01:45:25 +0000 With 1.1 M3 build on mpc8315e-rdb, this issue doesn't happen.