CHANGELOG
Changelog for package ament_cmake_google_benchmark
1.3.11 (2024-11-25)
1.3.10 (2024-07-26)
1.3.9 (2024-05-15)
1.3.8 (2024-02-16)
1.3.7 (2024-01-24)
1.3.6 (2023-11-13)
1.3.5 (2023-06-22)
1.3.4 (2023-04-25)
1.3.3 (2022-11-07)
1.3.2 (2022-05-17)
1.3.1 (2022-03-28)
1.3.0 (2022-02-17)
Update forthcoming version in changelog
Contributors: Audrow Nash
1.2.1 (2022-01-14)
Resolve various ament_lint linter violations (#360) We can’t add ament_lint linters in ament_cmake in the traditional way without creating a circular dependency between the repositories. Even though we can’t automatically enforce linting, it’s still a good idea to try to keep conformance where possible.
Update maintainers to Michael Jeronimo and Michel Hidalgo (#362)
Contributors: Audrow Nash, Scott K Logan
1.2.0 (2021-10-29)
1.1.4 (2021-05-06)
1.1.3 (2021-03-09)
1.1.2 (2021-02-26 22:59)
1.1.1 (2021-02-26 19:12)
1.1.0 (2021-02-24)
Serialize benchmarks within CTest by default (#308)
Contributors: Scott K Logan
1.0.4 (2021-01-25)
1.0.3 (2020-12-10)
1.0.2 (2020-12-07)
Handle runtime failures in Google Benchmark (#294) This change will handle runtime failures in Google Benchmark by propagating error information from Google Benchmark to both CTest and the Jenkins benchmark plugin.
Use consistent string format and resolve flake8 (#295) Follow-up to a5fb3112b5c46c42b1824c96af4171d469eb13bf
Make ament_cmake_test a dep of ament_cmake_google_benchmark (#293)
Catch JSONDecodeError and printout some debug info (#291)
Update package maintainers. (#286)
Contributors: Michel Hidalgo, Scott K Logan, brawner
1.0.1 (2020-09-10)
Make AMENT_RUN_PERFORMANCE_TESTS a CMake option (#280)
Skip performance tests using a CMake variable (#278) These tests can be fairly heavy, so we don’t want to run them by default. It would be better if there was a way to skip the tests by default in such a way that they could be specifically un-skipped at runtime, but I can’t find a mechanism in CMake or CTest that would allow us to achieve that behavior without leveraging environment variables.
Handle Google Benchmark ‘aggregate’ results (#276) Previously, I assumed all results generated by Google Benchmark were of ‘iteration’ type. Now that I have more experience with Google Benchmark, I’ve started generating aggregate results, which contain some different properties. This change adds support for aggregate results and should make it easy to add any other result schemas we encounter in the future. For forward-compatibility, unsupported types will generate a warning message but will not fail the test. This makes the conversion tolerant to Google Benchmark adding new measures for existing mechanisms.
Initial Google Benchmark results conversion (#275)
Contributors: Scott K Logan