summaryrefslogtreecommitdiff
path: root/libs/gui/BufferQueueThreadState.cpp
diff options
context:
space:
mode:
author Yeabkal Wubshit <yeabkal@google.com> 2024-10-02 08:10:19 +0000
committer Yeabkal Wubshit <yeabkal@google.com> 2024-10-02 08:59:34 +0000
commit12c4ce6b908ba89d4a6a19b0403f30cc5c2561a1 (patch)
tree7e1da25741d96c5a4434a2fc62d7160b90f32011 /libs/gui/BufferQueueThreadState.cpp
parent8072f42c35dc614749f9696762555b66696599e8 (diff)
Use std::string for test expresslog std::map
In ag/29575518, we wrapped expresslog Counter calls with an std::function to help with testing. In the tests, we used a map, with the key being the Counter key as a char*, and the value being the aggregated count. This approach caused test failures when we try to enable the flag in trunk_staging. After investigation, we realized that this is caused because the key of the std::map is the literal pointer (char*), meaning that the same string literals may be counted as different std::map keys in the test map. To mitigate this, we're now using std::string as the test map key type instead. Because the hash/equality of std::string depend on the string's content (instead of the pointer), the test issues are expected to resolve. Bug: 370353565 Test: atest RotaryEncoderInputMapperTest Flag: com.android.input.flags.rotary_input_telemetry Change-Id: Ibc89aeaf96e4627876929b76fe40b4a4a535b3df
Diffstat (limited to 'libs/gui/BufferQueueThreadState.cpp')
0 files changed, 0 insertions, 0 deletions