Jenkins failure:

04:57:30     creating build/temp.linux-x86_64-3.7/psutil
04:57:30     gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPSUTIL_POSIX=1 -DPSUTIL_VERSION=560 -DPSUTIL_LINUX=1 -DPSUTIL_ETHTOOL_MISSING_TYPES=1 -I/usr/include/python3.7m -c psutil/_psutil_common.c -o build/temp.linux-x86_64-3.7/psutil/_psutil_common.o
04:57:30     unable to execute 'gcc': No such file or directory
04:57:30     error: command 'gcc' failed with exit status 1

The error appears to come from pip3 install --user -r ./requirements.txt in waiverdb-build.Jenkinsfile.

@rayson, @gnaponie: we likely need to include gcc, python-devel, headers and what not in waiverdb-jenkins-slave image.

we likely need to include gcc, python-devel, headers and what not in waiverdb-jenkins-slave image.

Rather than that, the waiverdb.spec needs to be updated and then openshift/containers/jenkins-slave/Dockerfile rebuilt.

It's better to avoid pip install and building/installing dependencies when tests need to be run.

Hmm, I don't seem to have permission to access the base image.

# copy login command from https://registry-console.engineering.redhat.com/registry
> docker login -p ... -e unused -u unused docker-registry.engineering.redhat.com
Flag --email has been deprecated, will be removed in 1.14.
Login Succeeded
> cd openshift/containers/jenkins-slave
> docker build -t waiver-test .                                                                                              
Sending build context to Docker daemon 3.584 kB
Step 1/10 : FROM docker-registry.engineering.redhat.com/devops-automation/rad-slave-fedora-29:latest
Trying to pull repository docker-registry.engineering.redhat.com/devops-automation/rad-slave-fedora-29 ... 
unauthorized: authentication required

I updated the C3I Jenkins job to ignore the error of installing ./requirements.txt.
I will keep an eye on it. If installing ./requirement.txt cause more trouble than benefits, I will remove it.

@gnaponie You can try rebasing to the latest master to match the new dependencies introduced by #291.

@lholecek That's weird. The base image should be accessible by anonymous users.

If installing ./requirement.txt cause more trouble than benefits, I will remove it.

How to handle PRs that add a new dependencies? The container image for Jenkins slaves needs to be updated or the Jenkins build would need to have a way to install the new dependency (pip way is good now because it doesn't require sudo).

If installing ./requirement.txt cause more trouble than benefits, I will remove it.

How to handle PRs that add a new dependencies? The container image for Jenkins slaves needs to be updated or the Jenkins build would need to have a way to install the new dependency (pip way is good now because it doesn't require sudo).

Currently it is impossible to install rpms because we don't have the root access to openshift pod. The pip way works most time except occasions that required c libraries are missing.

@gnaponie Hi, just a reminder:

Currently WaiverDB C3I pipelines don't run because there is an outage of Internal registry (docker-registry.engineering.redhat.com). See https://redhat.service-now.com/surl.do?n=PNT0504850.

Oh ok. Good to know, thanks. I've stopped the build I've run.

Hi @gnaponie ,
C3I Jenkins build failed with message:

waiverdb/events.py:15:0: E0401: Unable to import 'fedmsg' (import-error)

fedmsg is deprecated by #291 . Did you rebase your PR to the latest master branch?

@gnaponie Please refer to https://pagure.io/freshmaker/pull-request/373, as the Jenkins file seems to be very similar. The latest commit here in this PR is 9579886, but Jenkins job does some checkouts of master in the early phases. Not sure if it's intended or not, so I just wanted to inform you.

+1

Commit fc5cea27 fixes this pull-request