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

Add test failure troubleshooting docs #3528

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

kat-lsg-dev
Copy link

This adds information for LISA users on how to troubleshoot test failures and how to understand the console output and logs.

Thank you for Lili Deng and Chi Song who created the images and provided information to make this documentation.

@@ -0,0 +1,116 @@
Troubleshoot Test Failures
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please merge understand_results page into this one. It doesn't need a separated page to explain test status.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This screenshot is from azure storage, not in upstream lisa. Please use a screen shot from the upstream lisa.

Overview
--------

To understand a test failure, the recommended troubleshooting path is:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please explain more on why we recommend this. Because the test results should be able to troubleshoot most issues, and it's simple to read and get.


- `Overview <#overview>`__
- `Test results <#test-results>`__
- `Console output <#console-output>`__
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sections should follow what we recommended in the Overview. Like the "Error Message" section, it explains the test results, and where the error message can be found, and so on.

- `Overview <#overview>`__
- `Test results <#test-results>`__
- `Console output <#console-output>`__
- `Log Folder Structure <#log-folder-structure>`__
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log folder structure should be a sub-topic of Log files.

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

Successfully merging this pull request may close these issues.

2 participants