[test] Provide control of stack trace generation in tests

Collecting and emitting stack traces is not free. Tests that run in
debug configurations may time out solely due to this cost. There are
many cases in which stacks traces may never be visible to the developer.
One such case is in a death test's child proc: the child process is
expected to crash, so any stack traces generated for this are expected
and hidden.

In https://crrev.com/1246434 we suppressed the generation and printing
of stack traces in CHECK/LOG(FATAL)/etc messages in death tests. In
https://crrev.com/1272204 we replaced this with a change to `StackTrace`
itself to suppress output in any case in death tests. In this change, we
go one step further as follows:

By default, `base::debug::StackTrace` will no longer collect a trace in
a death test, and printing an empty stack trace will no longer do any
processing. Tests that require a stack trace in a death test may use
base::debug::OverrideStackTraceOutputForTesting to force-enable
generation and output of traces in death tests. Additionally, some
non-death tests may also result in the generation and emission of stack
traces that will never be seen (e.g., those that use
`EXPECT_FATAL_FAILURE`). These tests can use the same test helper to
suppress the generation and output of stack traces in non-death tests.

Bug: 41490321
Change-Id: I036e333ec66731ee125f2e80c2e05b002b339e7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5377866
Auto-Submit: Greg Thompson <grt@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Reviewed-by: Alberto Juarez <albertojuarez@google.com>
Reviewed-by: Francois Pierre Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1276095}
11 files changed
tree: c30402afe546464481cd9257588fa6123b888e87
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.