- Infra - oVirt List Archives

[JIRA] (OVIRT-920) Add a standard-CI job and button "build-scratch-artifacts"
by Yedidyah Bar David (oVirt JIRA) 07 Dec '16

07 Dec '16

Yedidyah Bar David created OVIRT-920: ---------------------------------------- Summary: 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-919) Fwd: CI slaves extremely slow - overloaded slaves?
by Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-919: ------------------------------------ {quote} ... snip ... 17:19:49 1.105877 seconds This test runs in 0.048 seconds on my laptop: ... snip ... Ran 4 tests in 0.189s {quote} [~nsoffer(a)redhat.com] Lets make sure we're comparing apples and apples first, did you run this using "{{mock_runner.sh}}" on your laptop? Perhaps try this in a VM on your laptop? {quote} 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. {quote} Not sure where nested kvm comes into play here, "{{check_patch.sh}}" runs on plain VMs. (As an OT side-note: Are you sure nested VMs should be slower CPU-wise? AFAIK those are just VMs with nested I/O routing... it may be interesting to check this with Lago...) WRT "overloaded slaves" - that can hardly happen, no slave ever runs more then one job at at time. The hypervisors themselves may be loaded, we'll try to gather some more data here: [~ngoldin(a)redhat.com] Do we have hypervisor load graphs in Graphite? [~ederevea] What is out vm/core ratio? Are we running oVirt DWH? maybe it can help us here... {quote} 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. {quote} As far as machines go, our upstream hardware is quite beefy these days, so lets not jump to any conclusions. More data is needed, what is this test actually doing? is this pure CPU, or is there so I/O involved here as well? [~rgolan(a)redhat.com] Are there any oVirt features that can help us here? Higher priority VMs? Realtime? Better scheduling? > 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 Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-919: ------------------------------- Labels: hypervisors performance slaves standard-ci (was: ) > 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 Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-919: ------------------------------- Component/s: Jenkins > 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 > > 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

CI slaves extremely slow - overloaded slaves?
by Nir Soffer 07 Dec '16

07 Dec '16

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

2 1

[JIRA] (OVIRT-919) Fwd: CI slaves extremely slow - overloaded slaves?
by Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-919: ------------------------------- Description: 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 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ was: More discussion and tracking needed, moving to Jira (please put any further discussion there) ---------- Forwarded message ---------- 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 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ > 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 > Reporter: Barak Korren > Assignee: infra > > 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 > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-919) Fwd: CI slaves extremely slow - overloaded slaves?
by Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-919?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-919: ------------------------------- Description: 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 was: 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 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ > 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 > Reporter: Barak Korren > Assignee: infra > > 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 Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

Barak Korren created OVIRT-919: ---------------------------------- Summary: 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 Reporter: Barak Korren Assignee: infra More discussion and tracking needed, moving to Jira (please put any further discussion there) ---------- Forwarded message ---------- 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 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-918) Special characters escaped in Jenkins manual triggering of CI
by Barak Korren (oVirt JIRA) 07 Dec '16

07 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-918: ------------------------------------ That is not a job, its a special screen that is part of the [Gerrit trigger plugin|https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger] We do seem to be a couple releases behind (2.21.1) the latest plugin release (2.23.0). So we may upgrade, but nothing in the plugin changelog implies that this issue was dealt with. We may as well just go and report this on the [Jenkins issue tracker|http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&r…] > Special characters escaped in Jenkins manual triggering of CI > ------------------------------------------------------------- > > Key: OVIRT-918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-918 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Allon Mureinik > Assignee: infra > > If a subject of a change has special characters, they get HTML-encoded when presenting it in the Jenkins manual trigger job. > See screenshot for an example: > http://imgur.com/G1M7vNu -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

oVirt infra daily report - unstable production jobs - 161
by jenkins＠jenkins.phx.ovirt.org 07 Dec '16

07 Dec '16

------=_Part_41_1154478995.1481151609825 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/161//artifact/exported-a… Cheers, Jenkins ------=_Part_41_1154478995.1481151609825 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 07/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el6-x…">ovirt-guest-agent_master_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_41_1154478995.1481151609825--

1 0