- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 1065
by jenkins＠jenkins.phx.ovirt.org 10 Jan '20

10 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1065//artifact/exported… Cheers, Jenkins

1 0

[CQ]: baf4505 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 09 Jan '20

09 Jan '20

Change baf4505 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/baf4505295a15a79ca9b83411d9a0b… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17967/

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ for infra issue i am not certain, we need to ask Evgheni maybe. because 2 runs produced the same results. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ so if it’s only decided in the stage itself, I think that’s safe enough to limit for 5h. you can’t alter it on runtime.. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Dusan Fodor (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Dusan Fodor edited comment on OVIRT-2853 at 1/9/20 8:59 AM: ------------------------------------------------------------ Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been an infra issue. was (Author: dfodor): Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been in infra issue. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Dusan Fodor (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Dusan Fodor commented on OVIRT-2853: ------------------------------------ Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been in infra issue. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ You can define stages in the stdci.yaml file and under the build-artifacts stage you can define: timeout: 5h > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #233
by jenkins＠jenkins.phx.ovirt.org 09 Jan '20

09 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9ad7dff1d96ad50a54d021d167c842cbffe7d014 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9ad7dff1d96ad50a54d021d167c842cbffe7d014 Commit message: "gate: Move test suit to use DSL & container" > git rev-list --no-walk 9ad7dff1d96ad50a54d021d167c842cbffe7d014 # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5525763586160551627.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-sclo-rh-release-7.6-el7 yum + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7 /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base + check_yum_sync_needed centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-sclo-rh-release-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 1064
by jenkins＠jenkins.phx.ovirt.org 09 Jan '20

09 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1064//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 106097,1 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 08 Jan '20

08 Jan '20

Change 106097,1 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106097/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17957/

1 0