You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some ThreadPool unit tests that test crashed tasks were
missing printk logs to indicate the crashes were expected.
This creates confusion when debugging printk logs. This commit
adds the traces to indicate the crashes are expected and are part
of the test.
Change-Id: I38d2d886cfd73106e32fb4e461bba3d5a39a8032
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/83783
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Christian R Geddes <crgeddes@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Nicholas E Bofferding <bofferdn@us.ibm.com>
Reviewed-by: Daniel M Crowell <dcrowell@us.ibm.com>
0 commit comments