search

gluster / project-infrastructure

Issues related to GlusterFs infrastructure components.
0 stars 0 forks source link

Update Gcov and Clang versions to latest #90

Open msaju opened 4 years ago

msaju commented 4 years ago

Gcov and Clang versions are on old versions. Need to update to latest.

mscherer commented 4 years ago

Can you explain a bit more about gcov ? the lcov test is run on centos 7, but until the tests are working on Centos 8 and/or Fedora 32, we can't move it to a newer version. For clang, I have submitted a patch to move that to F32.

mscherer commented 4 years ago

Reopening, the issue was closed by automation github side (seems that GH is not smart enough to understand english when i say "partial fix" :p ).

msaju commented 4 years ago

Ok, will raise a separate ticket for gcov as soon as the centos 8 tests passes.

msaju commented 4 years ago

Noticed that the latest CLANG scan is giving "Zero" bugs. Is it WIP ?

mscherer commented 4 years ago

No, seems to be a bug. I will take a look, I guess something changed in a subtle way that make jenkins fail without error.

mscherer commented 4 years ago

09:49:35 configure: error: libuuid is required to build glusterfs

so it seems that if mock fail to build, our test continue normally. I guess we need a way to make it fail in a more visible way. We could fail if there is 0 bugs found, but that seems wrong (like, what if one day, we have perfect code ?)

mscherer commented 4 years ago

So https://build.gluster.org/job/clang-scan/1197/ work, "87 bugs found" so 4 more than last one. I guess that mean it is picking new errors, so that's good.

msaju commented 3 years ago

Ok, will raise a separate ticket for gcov as soon as the centos 8 tests passes.

The Cent OS 8 regression is passing now. Is it required to create a new ticket for the GCOV?.