Has anyone ever looked into printing out stack traces when layout tests
crash? Of the couple layout test crashes I've investigated, I think most
could have been solved just by having a stack trace. I'm not really sure
what's involved or if anyone's looked into this, which is why I'm asking.
This could be especially helpful for flaky tests that crash.
J
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
