Age | Commit message (Collapse) | Author | Files | Lines |
|
MongoDB sorts the results in memory, and the default mem limitation is
32M, if the sort operation consumes more than that it will return an
error:
OperationFailure: Executor error during find command: OperationFailed
Sort operation used more than the maximum 33554432 bytes of RAM. Add an
index, or specify a smaller limit.
To solve this problem, here we leverage aggregate() and
allowDiskUse=True, it is said will not be limited by memory
Change-Id: Id698ad1d02912e8b350a33a926fcccc390814fcc
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
In this patch, pagination is supported, so you can go through results
leveraging: http://testresults.opnfv.org/test/api/v1/results?page=2
Change-Id: Ibe31c787643f27dbb06c4899e713b3c8e716e784
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
filter of 'Start Date' & 'End Date' in Community Results page now works,
currently, only 20 records will be shown due to pagination is not
supported.
From server side, query from date to date is supported now, query as:
/api/v1/results?from=2016-11-01%2000:00:00&to=2017-06-01%2023:59:59
Change-Id: I482b117129dbae38fa5a2858a86442c80d87d19e
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
show latest 20 results in cummunity results page.
Because pagination is not supported, pagination related buttons
are forbiddened now
Change-Id: I3d94fc1b89845b6583dd40fe86d69407adfd2e6c
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I2ee4c3be6f34ce12530450cd22f2561c458685f9
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I1aa61c5d1b057b5a53cf6369b26605867a4d092e
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I994feb7bf340c9e48bebe9fdf3dc3a76bc254652
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I109ef9550a57e218b6f5c9196812b33133d34134
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I3045dc690e0bc1186f5c548cb533462dd03130d9
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
TestAPI violate import rule of OpenStack Style a lot, like
Do not import objects, only modules
Do not import more than one module per line
Alphabetically order your imports by the full module path
This patch is mean to fix them.
Change-Id: Ia05b944a74b3f443c9101a9840f613f9a6f5ae49
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
This is being done because titles have become so long in index of
documentation [0] that they don't fit in one line.
[0] http://artifacts.opnfv.org/releng/docs/testapi.html
JIRA: FUNCTEST-704
Change-Id: I046a21d7ceac6dc203ac71d169d4303095bdc69c
Signed-off-by: rohitsakala <rohitsakala@gmail.com>
|
|
Swagger codegen uses nicknames for defining titles in the api
documentation.
Link - https://github.com/OAI/OpenAPI-Specification/blob/master/versions/1.2.md
Change-Id: Ia35718b77dfcac53317384c4445225f28e505919
Signed-off-by: rohitsakala <rohitsakala@gmail.com>
|
|
Change-Id: Iec4e3db23cd44f30831e17c127eda74e9d9b5d14
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|