Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
centralize jjb related scripts
Change-Id: I4abeb06f17b48b8e7ac15803db0f3ce7eb0c1b93
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
When anteater runs it generates a shortlog containing any errors that
were encountered during it's run.
If no errors exist it will still create an empty file 'shortlog'. A
review containing no content will be attempt to be posted and fail with:
fatal: Argument "{COMMIT | CHANGE,PATCHSET}" is required
Instead of attempting to post nothing, the job should just skip
submitting a review.
Change-Id: I3feacb15e47dea204783053b3e67a9aa81ba164d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Fixes some final yamllint issues introduced by recent patchsets in apex
and armband.
JIRA: RELENG-254
Change-Id: I26b45d737f06c215413e29c92031d14e23967506
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I8d119fb0f925bfebd91cb18fb4c0a176fb9dd4ca
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Id2c105c5540848b545316ce132e19b74f8fd35f1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Iaccfa0df8f9f282a54712f61489af3029a91d44b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Adds fix-workspace-permissions wrapper in case StorPerf leaves
any files owned by root behind
Increases timeout to 45 as miminal run can take just over 30
minutes.
Change-Id: I85549a2246baa3a24686cf425850a8e7c0b645c8
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
|
|
Cleanup some unused parameter overrides, which were never in effect
in the first place. For CI PODs, we inherit only installer specific
parameters, so slave-label based overrides are ignored.
PODs:
- arm-pod5;
- arm-virtual2;
- ericsson-pod1;
- lf-pod2;
This reverts commit bb22c8c02df3e9d030ff64c304536c31b78a37a6.
This reverts commit fc26623f9d7f211a9e29e246a2b13bdae5b3982b.
Change-Id: Iee80ad8357f5126c4aa7510ed66ab6e79c20f3fc
|
|
While at it, add missing DEPLOY_SCENARIO for Fuel log collection job.
This will add some more useful info to each job description text.
Change-Id: I4936013dc23ed696ad4a526961b23031753aed2a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
JIRA: RELENG-254
Change-Id: I5b9fe931e20a84d80d9ce6bc565bfee1db2dbc32
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Ia18bb029bdb235c5e3a28bd3d0bf5f354d524769
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Icbfff8c0368c227451a09ac7f1f81df3e0f3563a
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The newly added euphrates stream had it's fields overindented.
JIRA: RELENG-254
Change-Id: I8d033966023fdecec3f03f2c74982f9de775ac08
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Idc05b81ebf8636a5d422e54b72ee58c039b1843c
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Iba2a7b5de9cb56c2cc6579fb9ff37b3242a0283f
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
JIRA: RELENG-254
Change-Id: I11aee517b2a8af8d2e2519642872c84ba494a335
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
Dovetail danube jobs don't need to be triggerred every day now.
Disable the timed trigger.
If need, they can be triggered manually.
Change-Id: I2f114cd17fcd27d0e34be0824be3fc0d072dbae9
Signed-off-by: xudan <xudan16@huawei.com>
|
|
not enough valid data in history for elastic check
Change-Id: Ie3bcd7cc186605a31a857130646468e6f1ca7dde
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Post-Danube branches (master, stable/euphrates) do not use an ISO
argument, so stop passing it.
While at it, fix some minor coding style and a wrong scenario default.
Change-Id: I1878f80e685efc2da07dedd1d2c05c51933da2ec
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
To align to the convention, Daisy now also provides iso format
artifacts for user to download instead of the bin format. So
need to upload iso to GS.
In future, the bin file can be eliminated to save storage space.
Depends-On: I6ddfe8e291ea8f6d673bd82c4df310d63f61a130
Change-Id: Ib97f93b043866174d5d63f122aa867b2af1c1424
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|
|
Drop the single quotes to regexp works as expected.
Change-Id: I2ea09be14bc83effdd5860fd35dda540b412cf59
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
'skip-deloyment'"
|
|
the goal is not to penalize scenario with few iteration due to
CI pipeline constraints
until now the top score was calculated on the base on 4 iterations, it means
whatever the number of iterations, we always consider the possible top score
based on at least 4 iterations
each case can get
- 3 points (last 4 iterations PASS)
- 2 points (more than 1 PASS over the last 10 days but 1 FAIL of the last 4)
- 1 point (at least 1 PASS over the last 10 days)
- no point (never work)
so if we consider a scenario with 10 cases, the top score is
30 = 10*3 (max points)
the coefficient to calculate the top score is not the number of iterations
- 1 iteration => possible top score 10
- 2 iterations => top score 20
- 3 iterations => top score 20
- 4 or more iterations => top score 30
previously top score was systematically 30
https://wiki.opnfv.org/plugins/servlet/mobile#content/view/6828617
Change-Id: I01102bc00766b7f5b58e73befa7d5328fcc895cc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|