URL: https://bugzilla.redhat.com/1564451
Creator: [email protected]
Time: 20180406T10:31:43

Description of problem:

Today there are many users who just report bug, and not followup much in gerrit for the fix. When the fix is posted, the bug gets updated, and automatically transitioned. But assuming it gets abandon'd due to inactivity or something else, bugzilla users won't even have a clue. So, it would be good to leave a note in bugzilla that patch is now abandon'd. So relevant people may take actions.

Additional info:

I am not sure if it should bother to transition back the status to ASSIGNED/NEW in that case. Lets keep that one for later. For now, just a update in bugzilla is good enough, saying "The patch is abandon'd due to inactivity" (not sure we can capture abandon click from browser as a event, even in that case, it should be noted in bugzilla.

Again, for now, not expecting github post for this. We will get to it later.

Disable clang-format build in dashboard which is shown in "Active Green Tick" and confusing with clang-scan job.

Currently in regression job, if a test times out, we are not storing the logs of the test executed so far. Storing them helps in debugging in case of spurious failures.

In the case of the failed tests, we get to know the failed step by looking at "prove" output, the same is not available for timed out tests. Having both of them eases out the failures which are not reproducible.

clang-format passes successfully but still shows a warning message on some
of the Pull Requests and suggest edits in the code that is not been
changed by respective PR.

https://github.com/gluster/build-jobs/blob/main/build-gluster-org/scripts/clang-format.py
Script doesn't fail for appropriate patches instead show a comment for all patches

Rename centos8-regression to gh_centos8-regression. There is no GH specific regression jobs for centos-8.

More details at https://build.gluster.org/job/line-coverage/

Clang scan-build on gluster code is failing consistently on our Jenkins infra [1]. The last successful run was on Feb 20.

In the console, the following errors were logged.

19:54:19 [clang-scan] $ /bin/bash /tmp/jenkins243441148106308409.sh
19:54:24 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:24 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:25 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:25 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:26 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:26 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:27 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:27 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:28 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:28 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:29 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:29 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:29 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:29 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:31 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:31 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:31 chown: cannot access 'clangScanBuildReports': No such file or directory
19:54:31 Build step 'Execute shell' marked build as failure
19:54:31 Publishing Clang scan-build results
19:54:31 Could not locate a unique scan-build output folder in: /home/jenkins/root/workspace/clang-scan/clangScanBuildReports
19:54:31 Performing Post build task...
19:54:31 Match found for :Building remotely : True
19:54:31 Logical operation result is TRUE
19:54:31 Running script  : sudo mock -r $MOCK_CHROOT --config-opts=dnf_warning=False --clean
19:54:31 sudo chown -R jenkins:jenkins clangScanBuildReports
19:54:31 
19:54:31 [clang-scan] $ /bin/sh -xe /tmp/jenkins1699908289264841451.sh
19:54:31 + sudo mock -r fedora-29-x86_64 --config-opts=dnf_warning=False --clean
19:54:32 ERROR: Could not find required config file: /etc/mock/fedora-29-x86_64.cfg
19:54:32 ERROR:   If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg
19:54:32 POST BUILD TASK : FAILURE
19:54:32 END OF POST BUILD TASK : 0
19:54:32 Finished: FAILURE

Disable 32-bit-build-smoke build job which is shwon in "Activ Green Tick" in the dashboard and confusing with gh_32-bit-build-smoke.

Since that's a job running on python 2 and we had issue with certificate, the job should ideally be rebased to run on a python 3 host. Any host would do the trick, no need to be in the cage. See #110

We are using Fedora 30 (which is end-of-life) with probably an old clang-scan. Please update to Fedora 32 and latest clang.

Disable centos7-regression which is shown in " Active Green tick " and confusing with gh_centos7-regression.

URL: https://bugzilla.redhat.com/1439706
Creator: [email protected]
Time: 20170406T12:16:11

Description of problem:

IMHO, We should remove this default name "Anonymous Coward".

There are people who wish to remain Anonymous and not wish to reveal their name during contribution.

First time contributor don't want to see their name like this :( just because they avoided github naming convention.

Suggestions is to use patch owner name directly or anything else.

This is just to remind the infra team to upgrade the chroot for the job gh_32-bit-build-smoke to fedora35

The upgrade at the moment is blocked due to the gcc warning : stringop-overread so we are currently running it on fedora-34-i386 chroot.

With this new change set we have also disabled the flag -Wno-address-of-packed-member which is no longer causing any issues.

So as of now we are working with the CFLAGS set to '-Wall -Werror'.

The job - staticanalysis-cppcheck is running on old master branch instead of devel.
There is one more job - https://build.gluster.org/job/cppcheck/ which is on devel branch but not run on a daily basis.

Please add the devel branch cpp check to run on a daily basis.