Skip to content

Msft dev#13

Open
MeritedHobbit wants to merge 8 commits intodevfrom
msft_dev
Open

Msft dev#13
MeritedHobbit wants to merge 8 commits intodevfrom
msft_dev

Conversation

@MeritedHobbit
Copy link
Collaborator

Changes

  1. Enhanced logging and error handling in command execution
  2. Map file parsing flow enhancements
  3. Enhanced regex path construction flexibility in log analysis

Details

  1. Improved the robustness of command execution by enhancing logging and error handling, restructured diagnostic data for better clarity and maintainability, and fixed issues in regex-based path construction to ensure accurate log analysis.
  2. Added JSON schema files for configuration and scenario recipes: Added JSON schema files to standardize configuration and scenario definitions across versions 0.7 and 0.8, including schemas for connection properties, test scenarios, and diagnostic error mappings.
  3. Updated existing diagnostic YAML tests to benefit from and comply with schema version 0.8, refined paths and connection types. Introduced new diagnostic scenarios showcasing regex-based searches and DRC assignment to enhance diagnostic coverage and validation.

- Created config_schema.json for version 0.7 and 0.8 to define connection properties and requirements for NodeManager, Inband, and RackManager.
- Introduced scenario_recipe_schema.json for version 0.7 and 0.8 to outline the structure for test scenarios, including test steps and Docker configurations.
- Added map_recipe_schema.json for version 0.8 to specify the structure for diagnostic error mappings.
- Updated existing diagnostic YAML test files to align with the new schema version 0.8, including modifications to paths and connection types.
- Introduced new diagnostic test scenarios to demonstrate regex searching and DRC assignment, ensuring comprehensive coverage of diagnostic functionalities.
… structure in diagnostics, and fix regex path construction in log analysis.
- Created new JSON files for scenario results, standardized results, and test results for the diagnostic scenario DiagSampleLogRegex9.
- Implemented logging for the test run, capturing detailed execution steps and outcomes.
- Added new YAML test scenario files for various diagnostic regex tests, ensuring consistent mapping to the updated map file.
- Updated existing YAML test scenarios to reference the new map file and improved descriptions for clarity.
- Enhanced logging output to include diagnostic codes and their occurrences for better analysis.
…ogRegex10

- Created new JSON log file `ocptv_DiagSampleLogRegex10_20260203_092930.json` to capture detailed test run logs.
- Added `scenario_results.json` to store structured results of the diagnostic analysis.
- Introduced `standardized_results.json` for standardized output of diagnostic results with additional metadata.
- Implemented `test_results.json` to summarize diagnostic codes and step results for the test scenario.
- Generated `test_run.log` to log the execution details and outcomes of the test run.
- Updated existing `test_run.log` to reflect new diagnostic codes and their corresponding messages.
- Added new YAML test scenario file `diag_sample_log_regex_10.yaml` to define the test steps and parameters for log analysis.
- Adjusted formatting in various files for better alignment and spacing.
- Added missing newlines at the end of several files.
- Updated comments for clarity and consistency.
- Enhanced logging in schema validation to include success and error messages.
- Improved placeholder resolution logic in path resolver.
- Organized import statements for better structure.
… DiagSampleLogRegex10; add .gitkeep files to Diagnostic and Health test directories.

Added schema validation report summary
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