Skip to content

0.8 Release#15

Open
MeritedHobbit wants to merge 16 commits into
mainfrom
dev
Open

0.8 Release#15
MeritedHobbit wants to merge 16 commits into
mainfrom
dev

Conversation

@MeritedHobbit

Copy link
Copy Markdown
Collaborator

Features & enhancements:

  1. Map File Schema at 0.8
  2. Recipe Schema at 0.8
  3. CPACT Schema Validation run (refer README)
  4. On direction from recipe, CPACT can now do log analysis as simple regex OR a json parse with regex
  5. On direction from recipe, CPACT can support regex on filenames provided for log analysis log paths.
  6. Recipe can have paths defined as shortcuts.
  7. All scenarios from within a test_dir can be executed.

v-ajitpanda and others added 16 commits December 17, 2025 22:23
- 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
- Introduced a new diagnostic recipe (diag_sample_log_regex_10.yaml) to extract device information from a JSON file using regex patterns, assigning diagnostic result codes based on error values.
- Modified diag_sample_log_regex_3.yaml to change the search string and diagnostic result code from 'Error_Code' to 'DRC' for consistency.
- Enhanced the map_recipe_schema.json to include schema versioning and improve the structure of the DRCs, ensuring required properties are enforced and additional properties are managed correctly.
This commit introduces a new log file generated during the diagnostic test run. The log captures the installation of the ERR driver, the start of OneDiag, and detailed results of the field diagnostics, including pass/fail statuses for various components. Notably, several components failed during the inventory checks, indicating issues that require further investigation.
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