Clang code coverage link is not showing results due to "502: bad gateway" (original) (raw)

Hi,

Link used: https://lab.llvm.org/coverage/coverage-reports/coverage/Users/buildslave/jenkins/workspace/coverage/llvm-project/index.html

Clang code coverage link is showing “502 Bad Gateway, nginx/1.18.0 (Ubuntu)”

Kindly suggest if link has changed, or something needs to be fixed in back-end infrastructure.

Thanks and Regards,
Vrukesh

Endill May 9, 2024, 2:27pm 2

CC @azhar
Hi Azhar,

If memory serves me well, you planed to change the way of how coverage reports are hosted, and to get the link on llvm.org updated to point to a new place.
Are you about to provide the new link?

azhar May 16, 2024, 6:33am 4

Hi @azhar - two questions related to coverage (sorry for pinging in this old thread):

1. How can I access raw coverage data for llvm-project, not just html?
2. Can I take a look at the coverage build bot configuration - to understand how it is setup? We are looking to set it up for llvm-prject/amd/comgr (which at the moment is built separately from the main llvm-project build) on our side.
   Thanks

Thanks - that’s it!

What about access to raw coverage data - has anyone known whether it is possible?

Currently the job just archives the reports. For example Artifacts of LLVM: Coverage Reports #134 : / [Jenkins]. The archive is 1.9GB uncompressed but it is surprisingly only HTML files.

I’m not involved in running that Jenkins instance, perhaps @gkistanova knows who runs it?

You (@kasaurov) could send a PR for llvm-zorg that they can review, if you want to add these artifacts.