[llvm] [Instrumentation] Fix EdgeCounts vector size in SetBranchWeights (PR #99064)

Mircea Trofin via llvm-commits llvm-commits at lists.llvm.org
Mon Aug 26 11:19:39 PDT 2024


mtrofin wrote:

> this is the failed test:
> 
> ```
> [830/1003] Running unit test libc.test.src.stdio.fscanf_test.__unit__
> FAILED: projects/libc/test/src/stdio/CMakeFiles/libc.test.src.stdio.fscanf_test.__unit__ /home/llvm-libc-buildbot/buildbot-worker/libc-x86_64-debian/libc-x86_64-debian-dbg/build/projects/libc/test/src/stdio/CMakeFiles/libc.test.src.stdio.fscanf_test.__unit__ 
> cd /home/llvm-libc-buildbot/buildbot-worker/libc-x86_64-debian/libc-x86_64-debian-dbg/build/projects/libc/test/src/stdio && /home/llvm-libc-buildbot/buildbot-worker/libc-x86_64-debian/libc-x86_64-debian-dbg/build/projects/libc/test/src/stdio/libc.test.src.stdio.fscanf_test.__unit__.__build__
> [==========] Running 1 test from 1 test suite.
> [ RUN      ] LlvmLibcFScanfTest.WriteToFile
> Segmentation fault
> ```
> 
> not sure if it is relevant.

Seems like it's a transient issue on that bot. (Also, a change in instrumentation shouldn't affect a libc test... normally. But the status of the subsequent build, https://lab.llvm.org/buildbot/#/builders/93/builds/4910,  is a stronger signal.)

https://github.com/llvm/llvm-project/pull/99064


More information about the llvm-commits mailing list