Age | Commit message (Collapse) | Author | Files | Lines |
|
Why is moon running against docs buids?
I don't know, but ts documentation release day.
Disabling moon
https://gerrit.opnfv.org/gerrit/#/c/45505/
Change-Id: Icb68bfc183347a98756f43073d6e5d9a0131144f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
as architecture is not considered as a constraints (unlike scenario or
installer) we need to work on the build tag to retrieve the data
but it is not possible to use regex directly in the API
so retrieveing the accurate results require extra processing
* based on build_tag, filter the results properly per scenario
* build a table build_tag time for a given scenario
* keep only the last 4 results
* evaluation criteria field
It would simplified if architecture could be declared as a constraint
then querying the resuls will not change and not require intermediate
steps
JIRA: FUNCTEST-880
Change-Id: Id4fe4f56babf0964d41e299905c804e0d837c3d7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
This patch also removes the --report flag when running a single
test case (functest-suite type of jobs)
Change-Id: Ic94fba53ced7c6f908905c02577e1b104f15afb7
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>
|
|
While at it, limit functest & yardstick to master and
stable/euphrates, trying to work around missing job references
in Danube scenarios on ZTE PODs.
Change-Id: I89de0c3b3c914e1ad735980a995e5cae625238be
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
apexlake was removed from yardstick codebase
Change-Id: I8eb826aa725dfb0e2c2c7a0bc1b15931fa245967
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
|
|
|
|
Change-Id: I1344241cc488481a64a7ba13da521537420a0c59
Signed-off-by: Kerim Gokarslan <kgokarsl@cisco.com>
|
|
1.6.0 is quite a bit out of date; Updating Yamllint to 1.8.2 will enable
some nicer feature of yamllint (like single line rule disables).
Change-Id: I88d1c14539516ccef4f5e2e7e95b0017503dd98f
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I88a6c87379ce330a90564bf174258d5e09d75c46
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
On rare occasions, Fuel/Armband verify jobs can get into a deadlock
on nodes with exactly 2 executors.
Add a build blocker to prevent such scenarios.
Change-Id: Ia00d88df0dd033264eaeb66e27188c62514b74d8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic2c4a52d58a7fdced5acfb9a706583646af7e56e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Recently htmlize.py was changed to a new directory. So, updated the path
of it in a build script
Change-Id: Ia409a36fdf38e16e9a66b73a07b7a78faaeb88fe
Signed-off-by: Sakala Venkata Krishna Rohit <rohitsakala@gmail.com>
|
|
* changes:
delete legacy update code
fix yamllint verify fail
|
|
|
|
update directory was employed to update TestAPI before auto deployment
is adopted, now it is useless and can be deleted.
Change-Id: I4e5ae84e80879cd9f711dc1d02224ae4f5902e49
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
fail record: https://build.opnfv.org/ci/job/opnfv-yamllint-verify-master/1050/console
Change-Id: Ic709b9a3d1d3642a3deebd930714a2ba2de22da6
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: BOTTLENECK-211
This patch is to fix the bug by adding -H flag to sudo, i.e.,
sudo -H pip install ...
Change-Id: Ie31f435e341ae9fe8f8e084696e8e1b7a05888d3
Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
|
|
Now the job functest-daisy-baremetal-daily-master runs on zte-pod3,
but the INSTALLER_IP in [1] belongs to zte-pod2.
Use virsh and arp commands to get the real INSTALLER_IP.
[1] https://build.opnfv.org/ci/view/functest/job/functest-daisy-baremetal-daily-master/151/console
Change-Id: I9e297b8f7a240437f81b4c3e2eab5949ac9d5e51
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
|
|
|
|
Change-Id: Id2e6b148f896eee5122339e501c8604e74ef774c
Signed-off-by: rpaik <rpaik@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: Id1fba783069c883868aa9cab6c8ea09485c411e5
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
All new patchsets should be free of yamllint violations.
JIRA: RELENG-254
Change-Id: Ia4f6d201837eb74d0c641b7ffb745c3df4327848
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
Change-Id: Iccf3e3202bf7fc090293454ddf8e6b93c2d3007c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
This patch is used to diasable jobs on Euphrates branch as there is only
one node assigned for the daily job. If the jobs on master and Euphrates
are enabled, the verify job is delayed.So inorder to avoid the delay for
the verify job, disabling the jobs on Euphrates.
Change-Id: Ib0eff4a1156858a73e4b889a61ac0cbd4ebe5ef0
Signed-off-by: Navya Bathula<navyax.bathula@intel.com>
|
|
To keep consistent with other testing project,
yardstick should change criteria value from 'SUCCESS' to 'PASS'
Change-Id: I8d8779927a74749e7c43df4e55e1888c49cbbbaf
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: Idc204f9f8c3e71f80d607ee55630cbea1e4f118a
Signed-off-by: zhouya <zhou.ya@zte.com.cn>
|
|
The trend tool will read installer field in scenario_history.txt
But now this field is fuel not fuel@x86 or fuel@aarch64.
So I change fuel -> fuel@x86 & fuel@aarch64.
Change-Id: I8e97e57febd559f65be559b16bceee5cf8268926
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
|
|
A string is added to the build that a security report is being
reported to Gerrit, even when it is not. This moves the string to just
before the line when the comment is posted so we aren't lying to
developers.
Change-Id: I73840d025e8be86b6ac02772b22b22c4abd29422
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
Since scenario data do not have a field named architecture,
So I choose pod_name for now.
For example:
pod_name: arm-pod5
I assume that it is based arm architecture
Change-Id: I92159a5e08b1ed80701494483fd9922dbd459193
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: BOTTLENECK-211
This patch is to fix the bug by adding -H flag to sudo, i.e.,
sudo -H pip install ...
Change-Id: Icdb187660cc1e08e134a79592e7454b77576f457
Signed-off-by: Gabriel Yu <Gabriel.yuyang@huawei.com>
|
|
|