| commit | 29ebc50befeae59d756e094d32811ad793413e48 | [log] [tgz] |
|---|---|---|
| author | Joshua Seaton <joshuaseaton@fuchsia.infra.roller.google.com> | Thu Feb 20 11:46:09 2025 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 20 11:47:25 2025 -0800 |
| tree | 1332cfc8a9edc0a1c73a0523c74744dc977bd4c9 | |
| parent | 1aa41db37b7983664a127a6cec736d5ed12ac139 [diff] |
[roll] Roll fuchsia [testing] Sanitize child component names in enumeration_test_adapter It is natural to give the name of the case in the enumeration config the same name as the canonical test case name, so we do that. Further. gtest will generate a parameterized test case name with slashes (like HmacTests/HmacTest.HMAC_SHA256Basic/0). Currently however - also out of want of a canonical name - the enumeration adapter forwards the name of the test case as the name of the child component in which it's run - and slashes are invalid in component names. Accordingly, we sanitize the constructed component names, replacing slashes with, say, underscores. This changes starts making an number of tests start to actually run instead of short-circuiting and erroring out. In the case of the oemcrypto-integration tests the runtime is now no longer reasonable in its current form, so we disable most of its cases for now (pending a closer look out-of-band from this change). In the case of the HMAC tests, these generate UBSan failures and more investigation is needed. Original-Bug: 397716819 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1210568 Original-Revision: f59d0264def6b83533a2a7913cf95c50df8cbca6 GitOrigin-RevId: fcae3e82adc320334a5d1cde0b6b3a62080be660 Change-Id: I55ce51195d51517f4c6fd9b124ead1aa4cc6b408
This repository contains Fuchsia's Global Integration manifest files.
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 in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.