When _expand_datacorpus is run without OSB having been set up (the script documentation indicates this is required, though), users see a confusing error message:
[ERROR] Cannot execute-test. Error in test execution orchestrator (Workload 'http_logs' is invalid.
Error details: [] should be non-empty
Instance: []
Path: deque(['indices'])
Schema path: deque(['properties', 'indices', 'minItems']))
There are other exceptions that show up if the http_logs data corpus is not present or if the corpus size is not provided.
Yet another issue is that, if the user chooses to run the script on Docker, the steps to do that are not documented. This case should be added to the help message, since the corpus needs to be generated within the Docker container.
To reproduce
Run expand-data-corpus.py on a host or in a Docker container without having run OSB first.
IanHoang
commented
1 month ago
Describe the bug
Description
When _expand_datacorpus is run without OSB having been set up (the script documentation indicates this is required, though), users see a confusing error message:
There are other exceptions that show up if the
http_logsdata corpus is not present or if the corpus size is not provided.Yet another issue is that, if the user chooses to run the script on Docker, the steps to do that are not documented. This case should be added to the help message, since the corpus needs to be generated within the Docker container.
To reproduce
Run
expand-data-corpus.pyon a host or in a Docker container without having run OSB first.