Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: ARMBAND-366
Change-Id: I6b513b6775b612bcc30327535e71827a7dd36ed9
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Openstack APIs response call is tacking very long on ARM
Work is being done on fixing the issue
Temporary increase functest timeout on x86 too because of COMPASS
JIRA: ARMBAND-366
JIRA: COMPASS-589
Change-Id: I355500da56c5a040324c0969237ac2decfd29edf
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Switching to multijob forces to increase executors which is too risky
so closed to the release.
It basically reverts the previous functest-daily-jobs.yml [1].
[1] git checkout 7f06f9492f4f8dd47669a553ef6e9c967fa29e8e jjb/functest/functest-daily-jobs.yml
7f06f9492f4f8dd47669a553ef6e9c967fa29e8e
Change-Id: I4a461108b11effe59e49108e1d95a9aae6e81ade
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It bypasses the missing senquential mode.
It also fixes exclusions about fds and patrole.
Several Functest could run in parallel but it's impossible from the
time being due to an xtables lock.
Change-Id: I831a8c995efbf2484afd86785f17f51981c921c1
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I454ff72c377a96aa769919348b27813ad434eb89
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I5289fedf52354f2cef6a3202df27d35acccb7c6c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
Change-Id: I1ce9e727a7f1448f657652a0f8d4bbab144b3ab9
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Iad86593d0b2711505999d5b0446d241cf56d5c8b
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
We are going to try this again. Once this is merged, I will need
to delete all the jobs that change job type and then re-merge
releng merge will be broken during this short window.
--- original commit message ---
Add support for functest tier with multijob
Add publishers separate for fetures and
all other functest tiers
Run functest features suits in a mutijob
Since there are no arm specific requirements,
remove arm-daily builders and jobs
Original patch by Delia Popescu <delia.popescu@enea.com>
Change-Id: I43422463c442ff6a18f6a98ab9909fc6c88e0259
JIRA: FUNCTEST-917
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
This reverts commit 7b9734aaca2fb04d1d8750b755a2880d60176889.
Change-Id: I5926d8013e57f2f0a68985b91aa8ab746bbbf1ab
|
|
Add support for functest tier with multijob
Add publishers separate for fetures and
all other functest tiers
Run functest features suits in a mutijob
Since there are no arm specific requirements,
remove arm-daily builders and jobs
JIRA: FUNCTEST-917
Change-Id: I92e3d7ca378dd6d293520c679c741de4bf336639
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I99da14477ab785475e425475fedca90a69eed8eb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Ia9bc336d43fe9ed47368f9aada0c6d9244a71683
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Icbdbe5a44660f498503ac84b323fd2a140ec3bbe
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
Change-Id: I8e88ab0598f43be8d0c9c4ad199dba91c1561f13
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Ib61cb40b04eed23ad276f261645d83ce7cf00629
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Functest has multiplied the testcases and integrates several ones
which are growing (e.g. snaps).
4 hours is reached if snaps or one vnf testcase fails (20 minutes).
https://build.opnfv.org/ci/view/functest/job/functest-compass-baremetal-daily-master/1695/console
Change-Id: I5e8b744d35b5253f6e7ac1310286ae374de1943b
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I2de88bcf0407b89579447159ed0ed233fbd62553
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
There is a former job template which was used for testing Alpine
containers at the beginning on 2 alpine-pods. That is not needed
any longer since we are running Alpine everywhere.
Also, this patch re-orders the builders.
Change-Id: Iabb41552f513773ebae1170232b8db1aeceb9a59
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
JIRA: RELENG-254
Change-Id: I89043a1149360d587588e8c887f88cc5192c1692
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
And add debug information for the suite jobs
Change-Id: I478a09c689b54f82246a72c19726576ff5aeaffd
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Also, improve suite job with alpine images.
Change-Id: I1367dea6b09361641c38ef91652acec5be4fbebb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Updated all the jobs that use functest-suite.
For single test cases, we need to know to which docker image
the test belongs to.
Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
So far we had 2 approaches:
* return Functest CI status: can be OK even if tests are FAIL
* return Functest Test status: can be FAIL even if all Functest tests are OK
(Fail in onboaraded tests)
A 3rd way is possible thanks to [1].
We consider only Functest status and Functest tests for the return statement
the return will be FAIL only if
* error in the framework
* error in Functest Tests
So concretely, if promise, Doctor can be FAIL, if Functest tests are OK, the
return will be PASS
[1]: https://gerrit.opnfv.org/gerrit/#/c/42245/
Change-Id: I6c7fbe99d888e43700ddb2dfc9bfd6cc9bfbaed6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
This change switches jobs to euphrates and removes danube jobs.
Change-Id: I9e53c595886b6214927c10c380a898e3c7510c7b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
regression reported by barometer project
1) --privileged=true no more set in docker run
2) wrong INSTALLER_IP -e INSTALLER_IP=192.168.122.169
3) ssh_key no more mounted -v /root/.ssh/id_rsa:/root/.ssh/id_rsa
Change-Id: Iccda9d57b7ea4c346ff26e9b2f74320bfe7eec95
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Functest Alpine not supported yet for aarch64 architecture.
Task for Armband project but until support could be done, the
traditionnal docker shall be used for armband tests
usage of alpine leads to errors [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-fuel-armband-baremetal-daily-master/214/console
Change-Id: I48e05a0c7cd97989784fd97348bd331425c4877e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
The following alpine containers will be launched one after the others:
- healthcheck
- smoke
- features
- vnf
Old container is kept for suite (which could be refactored later)
Jenkins exit condition (return_value) and push_test_logs to be checkeded.
Regarding the return condition, I did not reapply the mechanism that returns false
when one of the test suite is FAIL. This was misleading for lots of people as
for them, red means functest is FAIL.The argument was, if functest jenkins status
is blue, people believe that tests are PASS and do not consider the results, which
may be FAIL, which may be also misleading...
Due to the refactoring I think we can be more Functest Centric and consider
that if we succeeded in running the test, our CI status shall be PASS (same
behavior than other test projects..HA test FAIL in yardstick do not prevent blue
status).
Scenario owner must have a look at the reportign page to get more details.
Functest PASS means that tests have been succesfully launched, so they know that
there are available results
To summarize
previously Functest OK but 1 or more tests FAIL => red status in Jenkins
currently Functest OK but 1 or more tests FAIL => blue status in Jenkins
Regarding the push to artifacts, it should be transparent (volume) but the last
log links listed on huawei-virtual5 are broken [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-alpine-compass-huawei-virtual5-daily-master/27/consoleFull
Change-Id: I4ed036dda3daae3d46726e5946f9d04897bab9bb
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I134feba421d12c4ca428b098aaa2bf52b3dec0ca
|
|
1. Avoid exiting the script if an tier fails
2. Push logs to artifacts
Change-Id: Ia258994e4694bb71615f7adc18967afcc237813f
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
arm-pod3 pod name is changed to arm-pod5
arm-virtual1 pod name is changed to arm-virtual2
Change-Id: I6746fcdd52bbed5b6a61147d0abc5db64876dc97
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I5ce29cbb0786e83fbdf5bd014daf6686ec435562
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I8633353f3ca9bbf854e0d67760e6504524309d74
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: I96c7144578ee2e1f842e4bd22ffb79b9e1e54e4c
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: I1a27979cad590886fb5cdb039d69611a473cbe3c
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Since Functest doesn't post the output to
the console any more, we need the logs in
some jobs to troubleshoot.
Those logs are not stored for functest-suite
jobs by default.
This patch enables also lf-virtual2 and 3 where
some apex verify jobs are using this builder.
Change-Id: I5707d1540bed8df9b7c4457775d9877311ba0b33
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Since jenkins just imports the bash script at upload time, referencing
another script in the releng repo inside of bash doesn't work. We need
to split them out into their own builder includes.
Change-Id: Id120a338ae5ec48eaa285681463bff01677bf316
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- Remove any build blockers on 'apex-build-*' jobs.
- Adds script to download latest build artifacts before deployment.
- Make each deploy download the needed artifacts before running.
- ARTIFACT_VERSION now set to dev for verify builds to indicate tarball
should be uploaded to artifacts repo
- apex.yml jjb is now generated by using apex-jjb-renderer
- scenarios are managed in scenarios.yaml
JIRA: APEX-328
Change-Id: I4a51565686bd2011a310c3926d8260cd4641dca5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Because opera vnf test requires Open-O msb ip and the independency
of this test case, set specific docker env vars for compass4nfv
os-nosdn-openo-ha scenario.
Change-Id: I486e3896dc86d29cf93818b317675c088c1c5198
Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
|
|
Arm-pod3-2 is a second jenkins slave for arm-pod3.
This slave is arm while the old jenkins slave is x86.
Fatih requested for this slave to be renamed to arm-pod4
instead of arm-pod3-2, even if it's a slave for an existing pod
JIRA: ARMBAND-252
Change-Id: I5645edd7d774f763e5e72115851c7061bfafd344
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Change-Id: I1ae47f2105744bfea8c8c589f41282d1c4ae2159
Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
|
|
Armband Functest jobs timeout sometimes, mostly because of failing
tests which time out individually, adding to more than 180 min.
Therefore, increase the job timeout to 240 min.
Change-Id: I4829e14785f5dd7297f28dde436d5149a896d419
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
arm-pod3-2 is an aarch64 jenkins slave for the same POD as the existing
x86 jenkins slave arm-pod3. This commit adds jobs so we can deploy the
POD and run functest from the aarch64 jenkins slave.
These jobs are non-ci
JIRA: ARMBAND-241
Change-Id: Ie3b808a641e44649c02f3b75c83d79119217fdfe
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Also adds odl_l3-fdio-noha to daily job for Apex
Change-Id: I4732f8b905d0908124c2c65cd2ad3af92262d4b5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Fuel weekly jobs are created, calling fuel-deploy and functest weekly
jobs.
Experimental scripts have also been removed.
Change-Id: If492443e26248731df35e6b6cb5239fb2ae9a86a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|