Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a results.yml file after test run #1113

Closed
Tracked by #124
owaiskazi19 opened this issue Nov 22, 2021 · 4 comments
Closed
Tracked by #124

Create a results.yml file after test run #1113

owaiskazi19 opened this issue Nov 22, 2021 · 4 comments
Labels
enhancement New Enhancement

Comments

@owaiskazi19
Copy link
Member

Is your feature request related to a problem? Please describe

Coming from #1105 (comment). After running test.sh for Integration , BWC or Performance Test results.yml should be created which will consist of platform, architecture, version and the location.

Describe the solution you'd like

Generate a results.yml file which should have the content of build.yml and later can be loaded in uploadTestResults global variable to publish test results.

Describe alternatives you've considered

No response

Additional context

No response

@owaiskazi19 owaiskazi19 added enhancement New Enhancement untriaged Issues that have not yet been triaged labels Nov 22, 2021
@dblock
Copy link
Member

dblock commented Nov 22, 2021

It could probably also include some summary of results or pointers to other files.

@owaiskazi19
Copy link
Member Author

Summary of the test can be integrated using TestResults.

@gaiksaya
Copy link
Member

gaiksaya commented Nov 22, 2021

We have a summary file called <component-name>.yml but it lives in

https://ci.opensearch.org/ci/dbc/bundle-build/1.2.0/1127/linux/x64/test-results/10/<test-type>/<component-name>/<config>/test-results/<component-name>.yml

Maybe we can add those links as a part of https://github.com/opensearch-project/opensearch-build/blob/main/src/test_workflow/test_recorder/test_recorder.py#L39-L49

@abhinavGupta16 abhinavGupta16 removed the untriaged Issues that have not yet been triaged label Nov 30, 2021
@peternied
Copy link
Member

Closing this in favor of #1274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New Enhancement
Projects
None yet
Development

No branches or pull requests

5 participants