EDK II (mirror) https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Factions%2Fgithub-script-9 2026-03-31T22:24:43+00:00 2026-03-31T22:24:43+00:00 Doug Flick dougflick@microsoft.com 2026-03-30T21:17:58+00:00 urn:sha1:233eddb8e30d137597119a80a473c449cba3e351 lcov v2.0+ treats several gcov/source-related conditions as fatal errors that were previously warnings in v1.x. This causes coverage capture to abort when the build tree includes vendored third-party sources (e.g. OpenSSL) that produce gcov mismatches, missing source references, unexpected gcov output, or non-zero gcov return codes. Signed-off-by: Doug Flick <dougflick@microsoft.com> 2026-01-06T20:52:29+00:00 Michael D Kinney michael.d.kinney@intel.com 2026-01-06T19:31:07+00:00 urn:sha1:923a951e8a77ab62b089295a7e73b78b39940ab8 Add missing double quotes for lcov_cobertura --excludes option. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2025-12-22T08:09:04+00:00 Cosmo Lai cosmo.lai@intel.com 2025-11-28T10:00:51+00:00 urn:sha1:9e1a3bb474c9722bee1199b0da301dad55b602d9 For clang build, enable to generate coverage file under Build folder to merge coverage files of all module. Signed-off-by: Cosmo Lai <cosmo.lai@intel.com> 2025-09-28T23:38:21+00:00 Michael D Kinney michael.d.kinney@intel.com 2025-08-22T03:16:47+00:00 urn:sha1:3c454cf7d43c59f7ff0000ca6ac333e8f359673e Update HostBasedUnitTestRunner to generate merged Cobertura coverage.xml output file using CLANG code coverage data from -fprofile-instr-generate -fcoverage-mapping options. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2025-06-24T19:32:41+00:00 Michael D Kinney michael.d.kinney@intel.com 2025-06-19T05:05:23+00:00 urn:sha1:3f278768fab371ca2d9d2515a85894f8ee3194f9 Ignore mismatch errors for lcov 2.x in all locations that lcov is run. When building more complex unit tests, these mismatch errors are showing up in different phases of the code coverage collection. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2025-01-21T05:02:38+00:00 Michael D Kinney michael.d.kinney@intel.com 2024-12-04T03:39:56+00:00 urn:sha1:139cbb266b4847d1b63a20c568a5df9b26f7489b The environment variable `GTEST_CATCH_EXCEPTION` must be set to `0` for so all exceptions are handled by the address sanitizer and not GoogleTest. This allows stack back trace and other details to be logged by the address sanitizer so the source of the issue identified address sanitizer can be determined. The environment variable `ASAN_OPTIONS` must be set to `detect_leaks=0` to disable memory leak detection. The unit test frameworks may have memory leaks and some firmware code under test use cases may perform a memory allocation without a matching memory free as their expected behavior. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2024-12-05T00:05:47+00:00 Oliver Steffen osteffen@redhat.com 2024-12-04T11:10:53+00:00 urn:sha1:47ef19787356e003042d6f37d3853b9a47cb5d9e Detect the version of lcov and only apply version 2 workaround when needed. Fixes 61c714285f8c Signed-off-by: Oliver Steffen <osteffen@redhat.com> 2024-12-04T06:08:05+00:00 Oliver Steffen osteffen@redhat.com 2024-09-30T18:32:40+00:00 urn:sha1:61c714285f8cb83aa89b91798255f82260fa4ac2 lcov 2.0 and newer does additional error and consistency checking compared to previous versions. This can lead to CI jobs failing due to new/unexpected errors showing up. See: - https://edk2.groups.io/g/devel/message/116138 - https://github.com/linux-test-project/lcov/issues/209 - https://github.com/linux-test-project/lcov/issues/238 Signed-off-by: Oliver Steffen <osteffen@redhat.com> 2024-07-15T16:50:00+00:00 v-bhavanisu 144935558+v-bhavanisu@users.noreply.github.com 2024-07-12T17:45:58+00:00 urn:sha1:8e6ba0dcae40bfd4c191b2cd47e08f38186513d1 Some unit tests would fail to execute or execute and not produce any output logs. In these cases, the only output would be in the CI Log as `UnitTest Execution Error`. A UnitTest Execution Error should be considered the same as a unit tests test failing. Signed-off-by: Aaron Pop <aaronpop@microsoft.com> 2023-05-11T05:45:51+00:00 Gua Guo gua.guo@intel.com 2023-05-08T10:45:55+00:00 urn:sha1:6dd64168ed1f74c6226784233fa36a619a985a66 Windows command prompt have 8191 characters limitation, enhance it to make command too long can be resloved. Provide an example, if have too many cov files, it causes to run single command over the 8191 characters limitation. > OpenCppCoverage > --export_type binary:coverage.cov > --working_dir={workspace}Build > --input_coverage=AAA.cov > ... > --input_coverage=NNN.cov The solution is passing many coverage files in single command line to breaking it up into many command lines with one coverage file per command line in order to prevent single line is over to 8191 characters. - Command Line 1 > OpenCppCoverage > --export_type binary:coverage.cov > --working_dir={workspace}Build > --input_coverage=AAA.cov > --input_coverage=coverage.cov ... - Command Line N > OpenCppCoverage > --export_type. binary:coverage.cov > --working_dir={workspace}Build > --input_coverage=NNN.cov > --input_coverage=coverage.cov Cc: Michael D Kinney <michael.d.kinney@intel.com> Cc: Sean Brogan <sean.brogan@microsoft.com> Cc: Michael Kubacki <mikuback@linux.microsoft.com> Cc: Rebecca Cran <rebecca@bsdio.com> Cc: Liming Gao <gaoliming@byosoft.com.cn> Cc: Bob Feng <bob.c.feng@intel.com> Cc: Yuwei Chen <yuwei.chen@intel.com> Signed-off-by: Gua Guo <gua.guo@intel.com> Reviewed-by: Michael Kubacki <mikuback@linux.microsoft.com> Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>