The llvm-cov link in the left side column on llvm.org gives ERR_SSL_PROTOCOL_ERROR in Chrome. Is the coverage still being generated?
Yes, I’m able to browse the report with Safari on macOS, and the job is still active. Jenkins reports:
Would last have run at Saturday, April 24, 2021 1:37:55 AM PDT; would next run at Tuesday, April 27, 2021 1:37:55 AM PDT.
Maybe there’s an issue with the bot’s SSL cert? I’m not sure who to reach out to about that (perhaps @Azhar knows?).
vedant
Well, since we’re talking about the coverage report, anyone know what is run to generate the coverage report? i.e. How are we exercising the compiler? Skimming through the coverage report, I’m pretty sure some of the uncovered lines have llvm-lit tests. Are those run as part of the workload?
Philip
p.s. I’d really prefer an answer in terms of a link to docs or script location in code. I just can’t find said thing. 
Well, since we’re talking about the coverage report, anyone know what is run to generate the coverage report? i.e. How are we exercising the compiler? Skimming through the coverage report, I’m pretty sure some of the uncovered lines have llvm-lit tests. Are those run as part of the workload?
The bot just runs the check-{llvm,clang,lldb} targets. If you spot a discrepancy between the report and the test targets, please file a bug on bugzilla so we can track the issue.
Philip
p.s. I’d really prefer an answer in terms of a link to docs or script location in code. I just can’t find said thing.
Here’s how to configure a local coverage-enabled build: https://clang.llvm.org/docs/SourceBasedCodeCoverage.html#collecting-coverage-reports-for-the-llvm-project. I’ve also checked in the bot’s groovy script to llvm-zorg as of 2c899820.