December 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-920) Add a standard-CI job and button "build-scratch-artifacts"
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-920?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-920: -------------------------------------------- Epic Link: OVIRT-400 > Add a standard-CI job and button "build-scratch-artifacts" > ---------------------------------------------------------- > > Key: OVIRT-920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-920 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > I think it will be useful to have an option to very easily (such as > pressing a button in gerrit) to do a full build of a project, > similarly to current build-artifacts, but for a pending patch - so it > will not be collected by any publisher, and will keep its artifacts > for a short time (say, 2 days). > This will allow to use these artifacts for manual tests, perhaps > longer than check-patch, in case a developer wants to do them. > -- > Didi -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-920) Add a standard-CI job and button "build-scratch-artifacts"
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-920?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-920: -------------------------------------------- Epic Link: OVIRT-400 > Add a standard-CI job and button "build-scratch-artifacts" > ---------------------------------------------------------- > > Key: OVIRT-920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-920 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > I think it will be useful to have an option to very easily (such as > pressing a button in gerrit) to do a full build of a project, > similarly to current build-artifacts, but for a pending patch - so it > will not be collected by any publisher, and will keep its artifacts > for a short time (say, 2 days). > This will allow to use these artifacts for manual tests, perhaps > longer than check-patch, in case a developer wants to do them. > -- > Didi -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-922) Add new project to standard ci from github
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-922: -------------------------------------------- Epic Link: OVIRT-400 > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-911) Move repo closure to run in STD-CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-911?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-911: -------------------------------------------- Epic Link: OVIRT-400 > Move repo closure to run in STD-CI > ---------------------------------- > > Key: OVIRT-911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-911 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > Repo closure jobs are currently running on VMs. > We would like to change these jobs to run inside mocks as STD-CI. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-911) Move repo closure to run in STD-CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-911?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-911: -------------------------------------------- Epic Link: OVIRT-400 > Move repo closure to run in STD-CI > ---------------------------------- > > Key: OVIRT-911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-911 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > Repo closure jobs are currently running on VMs. > We would like to change these jobs to run inside mocks as STD-CI. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-919) Fwd: CI slaves extremely slow - overloaded slaves?
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-919: -------------------------------------------- Epic Link: OVIRT-403 > Fwd: CI slaves extremely slow - overloaded slaves? > -------------------------------------------------- > > Key: OVIRT-919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-919 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: hypervisors, performance, slaves, standard-ci > > From: Nir Soffer <nsoffer(a)redhat.com> > Date: 7 December 2016 at 21:33 > Subject: CI slaves extremely slow - overloaded slaves? > To: infra <infra(a)ovirt.org>, Eyal Edri <eedri(a)redhat.com>, Dan > Kenigsberg <danken(a)redhat.com> > Hi all, > In the last weeks we see more and more test failures due to timeouts in the CI. > For example: > 17:19:49 ====================================================================== > 17:19:49 FAIL: test_scale (storage_filesd_test.GetAllVolumesTests) > 17:19:49 ---------------------------------------------------------------------- > 17:19:49 Traceback (most recent call last): > 17:19:49 File > "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/storage_filesd_test.py", > line 165, in test_scale > 17:19:49 self.assertTrue(elapsed < 1.0, "Elapsed time: %f seconds" > % elapsed) > 17:19:49 AssertionError: Elapsed time: 1.105877 seconds > 17:19:49 -------------------- >> begin captured stdout << --------------------- > 17:19:49 1.105877 seconds > This test runs in 0.048 seconds on my laptop: > $ ./run_tests_local.sh storage_filesd_test.py -s > nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] > storage_filesd_test.GetAllVolumesTests > test_no_templates OK > test_no_volumes OK > test_scale 0.047932 seconds > OK > test_with_template OK > ---------------------------------------------------------------------- > Ran 4 tests in 0.189s > It seems that we are overloading the CI slaves. We should not use nested kvm > for the CI, such vms are much slower then regular vms, and we probably run > too many vms per cpu. > We can disable such tests in the CI, but we do want to know when there is > a regression in this code. Before it was fixed, the same test took 9 seconds > on my laptop. We need fast machines in the CI for this. > Nir -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-919) Fwd: CI slaves extremely slow - overloaded slaves?
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-919: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) Epic Link: OVIRT-403 > Fwd: CI slaves extremely slow - overloaded slaves? > -------------------------------------------------- > > Key: OVIRT-919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-919 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Labels: hypervisors, performance, slaves, standard-ci > > From: Nir Soffer <nsoffer(a)redhat.com> > Date: 7 December 2016 at 21:33 > Subject: CI slaves extremely slow - overloaded slaves? > To: infra <infra(a)ovirt.org>, Eyal Edri <eedri(a)redhat.com>, Dan > Kenigsberg <danken(a)redhat.com> > Hi all, > In the last weeks we see more and more test failures due to timeouts in the CI. > For example: > 17:19:49 ====================================================================== > 17:19:49 FAIL: test_scale (storage_filesd_test.GetAllVolumesTests) > 17:19:49 ---------------------------------------------------------------------- > 17:19:49 Traceback (most recent call last): > 17:19:49 File > "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/storage_filesd_test.py", > line 165, in test_scale > 17:19:49 self.assertTrue(elapsed < 1.0, "Elapsed time: %f seconds" > % elapsed) > 17:19:49 AssertionError: Elapsed time: 1.105877 seconds > 17:19:49 -------------------- >> begin captured stdout << --------------------- > 17:19:49 1.105877 seconds > This test runs in 0.048 seconds on my laptop: > $ ./run_tests_local.sh storage_filesd_test.py -s > nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] > storage_filesd_test.GetAllVolumesTests > test_no_templates OK > test_no_volumes OK > test_scale 0.047932 seconds > OK > test_with_template OK > ---------------------------------------------------------------------- > Ran 4 tests in 0.189s > It seems that we are overloading the CI slaves. We should not use nested kvm > for the CI, such vms are much slower then regular vms, and we probably run > too many vms per cpu. > We can disable such tests in the CI, but we do want to know when there is > a regression in this code. Before it was fixed, the same test took 9 seconds > on my laptop. We need fast machines in the CI for this. > Nir -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-904: -------------------------------------------- Epic Link: OVIRT-400 > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-905?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-905: -------------------------------------------- Epic Link: OVIRT-400 > lago_master_check jobs still require fc23 slaves > ------------------------------------------------ > > Key: OVIRT-905 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL in a couple of weeks we need to check if we can change this to newer Fedora versions or CentOS -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-905?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-905: -------------------------------------------- Epic Link: OVIRT-400 > lago_master_check jobs still require fc23 slaves > ------------------------------------------------ > > Key: OVIRT-905 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL in a couple of weeks we need to check if we can change this to newer Fedora versions or CentOS -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0