[roll] Roll fuchsia [unwinder] Update frame count check

Instead of estimating the number of total frames that should be present
after unwinding, we now find the frame corresponding to the start of
the test and verify that the required minimum number of frames
corresponding to the nested calls made are present. This avoids issues
that occur with varying frame counts due to compile time and link
time optimizations.

Original-Fixed: 318622080
Tests: fx test unwinder_tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/983967
Original-Revision: 4b9b7fe0e48957d955224c2065b387149f3e3f6b
GitOrigin-RevId: 9f648d82f7c38af285b77c103d30d47cb3e69a83
Change-Id: I1ac9a92e363bce0aeb73c115e2068be0211d1ac7
1 file changed
tree: 6418536e0d8560207df074216409ff2e376cf056
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.