symtest-cli 1.5.4__tar.gz → 1.6.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {symtest_cli-1.5.4/src/symtest_cli.egg-info → symtest_cli-1.6.0}/PKG-INFO +16 -5
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/README.md +14 -4
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/docs/design.md +85 -14
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/docs/design_en.md +109 -19
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/docs/user_manual.md +96 -14
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/docs/user_manual_en.md +129 -14
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/pyproject.toml +2 -1
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/SKILL.md +33 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/references/user_manual.md +129 -14
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/find.py +104 -8
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/run.py +15 -0
- symtest_cli-1.6.0/src/symtest/config/config_io.py +154 -0
- symtest_cli-1.6.0/src/symtest/config/config_schema.py +659 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/import_expander.py +26 -2
- symtest_cli-1.6.0/src/symtest/config/prepared.py +512 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/base_runner.py +20 -1
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/execution/executor.py +76 -17
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/execution/result.py +8 -2
- symtest_cli-1.6.0/src/symtest/core/execution/windows_job.py +339 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/history_store.py +41 -4
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/orchestration/sequence.py +13 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/orchestration/single.py +20 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/parallel_runner.py +58 -75
- symtest_cli-1.6.0/src/symtest/core/resource_manager.py +370 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/result.py +10 -1
- symtest_cli-1.6.0/src/symtest/core/system_memory.py +109 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/types.py +6 -0
- symtest_cli-1.6.0/src/symtest/file_comparator/csv_comparator.py +507 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/extractor_comparator.py +37 -9
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/file_comparator_base.py +35 -12
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/h5_comparator.py +211 -152
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/numeric_compare.py +130 -25
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/script_extract_comparator.py +5 -2
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/config_runner.py +20 -12
- symtest_cli-1.6.0/src/symtest/runners/parallel_config_runner.py +586 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/project_config.py +22 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0/src/symtest_cli.egg-info}/PKG-INFO +16 -5
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/SOURCES.txt +14 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/requires.txt +1 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/README.md +13 -0
- symtest_cli-1.6.0/tests/integration/file_compare/__pycache__/test_csv_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/integration/file_compare/test_csv_compare.py +522 -0
- symtest_cli-1.6.0/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/integration/parallel/test_parallel_runner.py +599 -0
- symtest_cli-1.6.0/tests/unit/__pycache__/test_config_preparation.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/__pycache__/test_h5_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_compare_command.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_find.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/test_find.py +91 -1
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_history_store.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/core/__pycache__/test_memory_flow.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_outputs_cleanup.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/core/__pycache__/test_resource_manager.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/core/__pycache__/test_windows_job.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/core/__pycache__/test_windows_memory.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_history_store.py +70 -0
- symtest_cli-1.6.0/tests/unit/core/test_memory_flow.py +246 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_outputs_cleanup.py +2 -1
- symtest_cli-1.6.0/tests/unit/core/test_resource_manager.py +465 -0
- symtest_cli-1.6.0/tests/unit/core/test_windows_job.py +258 -0
- symtest_cli-1.6.0/tests/unit/core/test_windows_memory.py +53 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_extractor_channels.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.6.0/tests/unit/file_comparator/__pycache__/test_numeric_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_numeric_parity.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_script_extract.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_extractor_channels.py +65 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_numeric_compare.py +172 -3
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_numeric_parity.py +24 -6
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_script_extract.py +21 -0
- symtest_cli-1.6.0/tests/unit/test_config_preparation.py +482 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_h5_comparator.py +226 -3
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_project_config.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/test_project_config.py +80 -0
- symtest_cli-1.5.4/src/symtest/config/config_io.py +0 -552
- symtest_cli-1.5.4/src/symtest/config/config_schema.py +0 -503
- symtest_cli-1.5.4/src/symtest/file_comparator/csv_comparator.py +0 -242
- symtest_cli-1.5.4/src/symtest/runners/parallel_config_runner.py +0 -347
- symtest_cli-1.5.4/tests/integration/file_compare/__pycache__/test_csv_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.5.4/tests/integration/file_compare/test_csv_compare.py +0 -166
- symtest_cli-1.5.4/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.5.4/tests/integration/parallel/test_parallel_runner.py +0 -208
- symtest_cli-1.5.4/tests/unit/__pycache__/test_h5_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.5.4/tests/unit/file_comparator/__pycache__/test_numeric_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/LICENSE +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/MANIFEST.in +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/setup.cfg +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/full_runner_example.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/extract_channels_script.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/my_analysis_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/my_channel_extractor.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_golden_file.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_simple.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_simple.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_steps.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/skill/references/field_reference.md +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/cli.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/migrate.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/schema.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/commands/validate.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/inheritance_expander.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/jsonc.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/migrate.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/config/normalize.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/config_loader.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/execution/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/last_run_store.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/orchestration/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/orchestration/accept.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/process_worker.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/sequence_state.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/setup.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/test_case.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/validation/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/validation/assertions.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/validation/result.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/core/validation/validator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/base_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/binary_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/factory.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/json_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/result.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/script_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/text_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/file_comparator/xml_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/logging_config.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/reporting/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/reporting/diagnosis.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/json_runner.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/parallel_json_runner.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/parallel_yaml_runner.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/runners/yaml_runner.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/html_report.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/junit_xml_writer.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/path_resolver.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest/utils/report_generator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/dependency_links.txt +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/entry_points.txt +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/top_level.txt +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-313.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-39.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-313.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-39.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/__pycache__/test_setup_module.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/conftest.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/demos/h5_filter_demo.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/demos/manual_report_example.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/demos/perf_parallel.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__init__.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-313.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-39.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/e2e/test_user_flows.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/circular_config_a.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/circular_config_b.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/hourglass_stdout_mismatch.txt +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/hourglass_stdout_sample.txt +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/inheritance_base.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/inheritance_chain.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/inheritance_circular.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/main_config.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/circular_config_a.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/circular_config_b.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_base.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_chain.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_circular.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/main_config.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/missing_fields.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/setup_main.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/setup_sub.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_golden_file.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_simple.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_simple.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_steps.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/sub_json_tests.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/sub_text_tests.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases1.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_with_setup.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_with_setup.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/missing_fields.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/mock_fail_script.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/mock_pass_script.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/setup_main.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/setup_sub.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/sub_json_tests.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/sub_text_tests.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/test_cases.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/test_cases.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/test_cases1.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/test_with_setup.json +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/fixtures/test_with_setup.yaml +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_new_cli_features.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_new_cli_features.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_new_cli_features.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_real_command_execution.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_real_command_execution.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_real_command_execution.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_binary_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_binary_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_binary_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_binary_compare.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_csv_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_csv_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_h5_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_h5_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_h5_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_h5_compare.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_json_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_json_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_json_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_json_compare.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_text_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_text_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_text_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_text_compare.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_xml_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_xml_compare.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/__pycache__/test_xml_compare.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/test_binary_compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/test_h5_compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/test_json_compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/test_text_compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/file_compare/test_xml_compare.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/__pycache__/test_depends_on.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/__pycache__/test_depends_on.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/parallel/test_depends_on.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/path_handling/__pycache__/test_spaces_in_paths.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/path_handling/__pycache__/test_spaces_in_paths.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/path_handling/__pycache__/test_spaces_in_paths.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/path_handling/__pycache__/test_spaces_in_paths.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/path_handling/test_spaces_in_paths.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/test_history_feature.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/test_new_cli_features.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/test_real_command_execution.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/integration/test_sequence.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/run_all.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_h5_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_h5_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_jsonc.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_migrate.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_migrate.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_compare_command.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_compare_command.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_find.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/commands/test_compare_command.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_architecture_guard.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_architecture_guard.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_case_env.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_case_env.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader_new_features.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader_new_features.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_config_loader_new_features.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution_new_features.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution_new_features.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution_new_features.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_history_store.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_history_store.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_last_run_store.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_last_run_store.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_last_run_store.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_model_v2.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_model_v2.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_orchestration_accept.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_orchestration_accept.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_parallel_results_echo.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_process_worker.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_process_worker.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_process_worker.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_sequence_state.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_sequence_state.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_validation_error.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_validation_error.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_validation_error.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_architecture_guard.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_assertions.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_case_env.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_config_loader.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_config_loader_new_features.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_execution.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_execution_new_features.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_last_run_store.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_model_v2.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_orchestration_accept.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_parallel_results_echo.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_process_worker.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_sequence_state.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_setup.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_validation_error.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/core/test_xfail.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_error_analysis.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_error_analysis.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_error_analysis.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_extractor_channels.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_hourglass_tangent_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_hourglass_tangent_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_hourglass_tangent_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_numeric_compare.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_numeric_parity.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_plugin_lifecycle.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_plugin_lifecycle.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_script_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_script_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_script_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_script_extract.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_workspace_plugins.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_workspace_plugins.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/test_workspace_plugins.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_error_analysis.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_hourglass_tangent_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_plugin_lifecycle.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_script_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_workspace_plugins.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-312.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_filter.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_filter.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_filter.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_tag_filter.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_tag_filter.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_test_case_tag_filter.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_with_deps.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/test_json_yaml_runner.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/test_test_case_filter.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/test_test_case_tag_filter.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/runners/test_with_deps.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_binary_comparator.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_cli.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_config_io.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_import_expander.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_inheritance_expander.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_jsonc.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_migrate.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_result.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/test_run_all.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_html_report.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_html_report.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_junit_xml_writer.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_junit_xml_writer.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_junit_xml_writer.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_report_generator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_report_generator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/__pycache__/test_report_generator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/test_html_report.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/test_junit_xml_writer.py +0 -0
- {symtest_cli-1.5.4 → symtest_cli-1.6.0}/tests/unit/utils/test_report_generator.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: symtest-cli
|
|
3
|
-
Version: 1.
|
|
3
|
+
Version: 1.6.0
|
|
4
4
|
Summary: Regression testing for CLI applications, with multi-step workflows and numerical file comparison.
|
|
5
5
|
Author-email: Xiaotong Wang <xiaotongwang98@gmail.com>
|
|
6
6
|
License: MIT
|
|
@@ -12,6 +12,7 @@ Requires-Python: >=3.9
|
|
|
12
12
|
Description-Content-Type: text/markdown
|
|
13
13
|
License-File: LICENSE
|
|
14
14
|
Requires-Dist: h5py<4.0.0,>=3.11.0
|
|
15
|
+
Requires-Dist: jsonschema>=4.18
|
|
15
16
|
Requires-Dist: numpy>=1.21.0; python_version < "3.12"
|
|
16
17
|
Requires-Dist: numpy>=1.26.0; python_version >= "3.12"
|
|
17
18
|
Provides-Extra: yaml
|
|
@@ -213,11 +214,21 @@ symtest run test_cases.json --parallel --workers 4
|
|
|
213
214
|
symtest run test_cases.json --parallel --execution-mode process
|
|
214
215
|
```
|
|
215
216
|
|
|
216
|
-
Thread mode
|
|
217
|
+
Thread mode supports CPU-token allocation, solver thread environment
|
|
217
218
|
variables, and longest-processing-time-first scheduling using estimates or
|
|
218
|
-
runtime history.
|
|
219
|
-
|
|
220
|
-
|
|
219
|
+
runtime history. On Windows, enabling `--history-dir` or declaring
|
|
220
|
+
`min_memory_mb` additionally turns on opportunistic memory admission: each
|
|
221
|
+
case's process-group commit-memory peak is measured via a Job Object and
|
|
222
|
+
stored in history, and a case starts only when CPU tokens, commit margin
|
|
223
|
+
(the case's own estimated demand plus a reserve), a physical-memory
|
|
224
|
+
watermark, and (only under potential peak crowding) a minimum startup interval
|
|
225
|
+
are all satisfied — queued
|
|
226
|
+
instead of launching into a memory shortage. Active tasks hold no full
|
|
227
|
+
peak reservations, so occasional overcommit is accepted (zero-OOM not
|
|
228
|
+
guaranteed). Process mode
|
|
229
|
+
provides execution isolation but does not yet use the resource scheduler.
|
|
230
|
+
Linux memory scheduling, priority semantics, and broader resource scheduling
|
|
231
|
+
remain active areas of development.
|
|
221
232
|
|
|
222
233
|
## CI and reports
|
|
223
234
|
|
|
@@ -186,11 +186,21 @@ symtest run test_cases.json --parallel --workers 4
|
|
|
186
186
|
symtest run test_cases.json --parallel --execution-mode process
|
|
187
187
|
```
|
|
188
188
|
|
|
189
|
-
Thread mode
|
|
189
|
+
Thread mode supports CPU-token allocation, solver thread environment
|
|
190
190
|
variables, and longest-processing-time-first scheduling using estimates or
|
|
191
|
-
runtime history.
|
|
192
|
-
|
|
193
|
-
|
|
191
|
+
runtime history. On Windows, enabling `--history-dir` or declaring
|
|
192
|
+
`min_memory_mb` additionally turns on opportunistic memory admission: each
|
|
193
|
+
case's process-group commit-memory peak is measured via a Job Object and
|
|
194
|
+
stored in history, and a case starts only when CPU tokens, commit margin
|
|
195
|
+
(the case's own estimated demand plus a reserve), a physical-memory
|
|
196
|
+
watermark, and (only under potential peak crowding) a minimum startup interval
|
|
197
|
+
are all satisfied — queued
|
|
198
|
+
instead of launching into a memory shortage. Active tasks hold no full
|
|
199
|
+
peak reservations, so occasional overcommit is accepted (zero-OOM not
|
|
200
|
+
guaranteed). Process mode
|
|
201
|
+
provides execution isolation but does not yet use the resource scheduler.
|
|
202
|
+
Linux memory scheduling, priority semantics, and broader resource scheduling
|
|
203
|
+
remain active areas of development.
|
|
194
204
|
|
|
195
205
|
## CI and reports
|
|
196
206
|
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
|---|---|
|
|
46
46
|
| `cli.py` / `commands/` | 子命令入口、参数装配与日志激活 |
|
|
47
47
|
| `core/` | TestCase 数据模型、断言引擎、单测试执行、Runner 基类(顺序 / 并行 / DAG)、`.symtest` 状态存储、Setup 插件体系 |
|
|
48
|
-
| `config/` | 配置 IO
|
|
48
|
+
| `config/` | 配置 IO、公共准备流程(`prepared.py`)、双形态 JSON Schema 契约与校验(draft 2020-12,`config_schema.py`)、import 展开、extends 继承、变量与占位符替换 |
|
|
49
49
|
| `runners/` | Config/JSON/YAML × 顺序/并行 的薄封装运行器 |
|
|
50
50
|
| `file_comparator/` | 比较器家族 + 工厂 + workspace 插件发现(详见 §6) |
|
|
51
51
|
| `utils/` | 路径解析、报告生成(文本 / 结构化 HTML)、JUnit XML 输出、项目级默认配置(`.symtest/symtest.json`) |
|
|
@@ -63,27 +63,52 @@
|
|
|
63
63
|
|
|
64
64
|
## 3. 配置管线
|
|
65
65
|
|
|
66
|
-
|
|
66
|
+
配置契约的唯一定义是 `config/config_schema.py`(JSON Schema draft 2020-12,双形态):
|
|
67
|
+
|
|
68
|
+
- **raw 形态**(`CONFIG_SCHEMA`):用户/AI 编写的原始配置文件;`abstract` 模板与 `extends` 继承用例允许缺少必填执行字段,完整性在展开后检查;`symtest schema` 导出该形态
|
|
69
|
+
- **展开形态**(`EXPANDED_CONFIG_SCHEMA`):import / extends / variables 全部解析后的有效配置;每个可执行用例必须完整
|
|
70
|
+
|
|
71
|
+
`validate` / `run` / `find` 三个入口共用公共流程 `config/prepared.py:prepare_config()`,结构检查失败即停止处理对应输入(后续代码不会见到畸形 dict):
|
|
67
72
|
|
|
68
73
|
```
|
|
69
74
|
raw JSON/JSONC/YAML 文件(.jsonc 由 config/jsonc.py 剥离注释与尾逗号)
|
|
70
75
|
│
|
|
71
76
|
▼
|
|
72
|
-
|
|
77
|
+
raw 形态 schema 校验 # 每个加载的文件(含 import 子文件):
|
|
78
|
+
# 字段名/类型/取值范围/执行形态互斥/未知字段
|
|
79
|
+
│
|
|
80
|
+
▼
|
|
81
|
+
expand_imports() # 递归展开 import 引用(合并 setup、注入 tags)
|
|
82
|
+
│
|
|
83
|
+
▼
|
|
84
|
+
重名用例检查 # extends 引用必须无歧义
|
|
85
|
+
│
|
|
86
|
+
▼
|
|
87
|
+
resolve_inheritance() # 解析 extends 继承链(deep-merge、去重 abstract)
|
|
73
88
|
│
|
|
74
89
|
▼
|
|
75
|
-
|
|
90
|
+
apply_variables() # 注入 --var 全局变量 + case-level variables,
|
|
91
|
+
# 递归替换 {placeholder} 占位符
|
|
76
92
|
│
|
|
77
93
|
▼
|
|
78
|
-
|
|
94
|
+
展开形态 schema 校验 # 展开后每个可执行用例必须完整
|
|
79
95
|
│
|
|
80
96
|
▼
|
|
81
|
-
|
|
97
|
+
语义检查 # error 级:depends_on 图(存在性/自引用/环)、
|
|
98
|
+
# outputs 路径边界;warning 级:命令可执行性、
|
|
99
|
+
# baseline 存在性、outputs 冲突
|
|
82
100
|
│
|
|
83
101
|
▼
|
|
84
|
-
parse_test_cases()
|
|
102
|
+
parse_test_cases() # 转换为 List[TestCase](命令路径解析)
|
|
85
103
|
```
|
|
86
104
|
|
|
105
|
+
以后新增普通配置字段只需:在 schema 中定义其合法性、在解析器中实现其转换,`validate` 即自动获得相应检查——不再维护独立的字段规则清单。
|
|
106
|
+
|
|
107
|
+
raw 形态的模板和继承用例允许局部 `execution` 字典,复用完整执行定义的字段约束,
|
|
108
|
+
仅延迟检查 `command/args` 必填项;`steps` 按整体替换语义仍要求所提供的 step 完整。
|
|
109
|
+
`load_config(..., workspace=...)` 将工作区传入公共流程,`find` 显式转交 CLI 工作区。
|
|
110
|
+
导入文件的读取异常在文件边界统一为带文件和引用来源的诊断,包含 YAML 解析异常。
|
|
111
|
+
|
|
87
112
|
### 3.1 Import 展开 (`import_expander.py`)
|
|
88
113
|
|
|
89
114
|
主配置文件通过 `"import"` 引用子配置文件:
|
|
@@ -104,12 +129,21 @@ parse_test_cases() # 转换为 List[TestCase](命令路径解析)
|
|
|
104
129
|
- extends 链上的 `variables` 收集后统一替换
|
|
105
130
|
- 循环继承检测
|
|
106
131
|
|
|
107
|
-
### 3.3
|
|
132
|
+
### 3.3 配置校验与公共准备流程 (`prepared.py` / `config_io.py`)
|
|
108
133
|
|
|
109
|
-
`
|
|
134
|
+
`validate_config()` 内部委托 `prepare_config()`;`run` 的配置加载阶段与
|
|
135
|
+
`find`(经 `load_config()`)走同一流程。同一份非法配置在 `validate` 与
|
|
136
|
+
`run` 中产生一致的错误,且 `run` 在执行任何命令之前退出。诊断信息带
|
|
137
|
+
文件路径与字段路径(jsonschema `json_path`),import 子文件中的错误能
|
|
138
|
+
定位到具体文件和字段。
|
|
110
139
|
|
|
111
|
-
- Error 级(影响 valid):JSON/YAML
|
|
112
|
-
|
|
140
|
+
- Error 级(影响 valid):JSON/YAML 语法、raw/展开双形态 schema 检查
|
|
141
|
+
(必填字段、类型、取值范围、执行形态互斥、未知字段)、import 目标存在性、
|
|
142
|
+
循环 import、用例重名、extends 目标存在性、循环继承、展开后用例完整性、
|
|
143
|
+
`outputs` 路径边界、depends_on 目标存在性/自引用/环
|
|
144
|
+
- Warning 级(不影响 valid):`command` 可执行性(PATH 查找)、
|
|
145
|
+
`compare_files` baseline 文件存在性、多用例声明相同 outputs 且无
|
|
146
|
+
depends_on
|
|
113
147
|
|
|
114
148
|
## 4. 执行语义
|
|
115
149
|
|
|
@@ -121,7 +155,7 @@ parse_test_cases() # 转换为 List[TestCase](命令路径解析)
|
|
|
121
155
|
- JSON/YAML Runner 仅注入不同的 config_loader,通用逻辑统一在顺序 / 并行通用运行器中
|
|
122
156
|
- xfail:`expected_failure=True` 时 `passed → xpassed`(意外通过,计入失败);任意非 passed → `xfailed`(预期失败,不计入失败)
|
|
123
157
|
- JUnit XML 状态映射:`xfailed → <skipped>`、`xpassed → <failure>`、`timeout → <error>`、`failed` 按消息类型分 `<failure>` / `<error>`
|
|
124
|
-
-
|
|
158
|
+
- 历史:耗时累计平均更新,写入前先按 `regression_threshold` 与旧均值做回归检测;内存峰值独立记录(`last_peak_memory_bytes` / `max_peak_memory_bytes` / `peak_memory_count` / `peak_memory_source`,字节),有效测量即可记录(含 failed / timeout),调度估算用历史最大值;`--update-history` 清除整条记录(耗时 + 内存)
|
|
125
159
|
- `--last-failed`:每次运行只覆写本次参与执行的用例状态,子集运行不丢失其余用例状态
|
|
126
160
|
|
|
127
161
|
### 4.2 测试双模式
|
|
@@ -132,12 +166,28 @@ parse_test_cases() # 转换为 List[TestCase](命令路径解析)
|
|
|
132
166
|
|
|
133
167
|
### 4.3 并行与资源调度
|
|
134
168
|
|
|
135
|
-
- LPT 策略:长任务先行;启用 history 时优先用 `.symtest` 历史 `avg_duration` 排序,其次才看声明的 `estimated_time
|
|
169
|
+
- LPT 策略:长任务先行;启用 history 时优先用 `.symtest` 历史 `avg_duration` 排序,其次才看声明的 `estimated_time`(兼容"只有内存记录、没有耗时字段"的历史条目,按 0 处理)
|
|
136
170
|
- `AtomicSemaphore` 资源池:`safe_capacity = max(1, cpu_count − 2)`;每个 case 按 `cpu_cores` acquire/release
|
|
137
171
|
- 按权重比例分配相对 CPU 核数,并自动注入 `OMP_NUM_THREADS` / `MKL_NUM_THREADS` / `NPROC`
|
|
138
172
|
- 环境变量优先级:`os.environ` < 调度器注入 < case 级 env(经 subprocess 注入,不改进程全局环境)
|
|
139
173
|
- 线程模式共享内存 + 结果/打印锁;进程模式经 process worker 隔离;可回退顺序执行
|
|
140
174
|
|
|
175
|
+
**Windows 内存感知调度——机会式准入**(线程模式 + Windows + 启用 `--history-dir` 或声明 `min_memory_mb` 时启用;其余情况走原 CPU-only 路径,行为不变):
|
|
176
|
+
|
|
177
|
+
- 内存需求估算优先级:显式 `min_memory_mb` > history 历史最大峰值 × 安全系数(默认 1.2,`memory_margin` 可配) > 可配置默认需求(`memory_default_demand_mb`,默认 4096 MB);不再整池独占
|
|
178
|
+
- `JointResourceManager` 联合资源池:CPU 令牌 + 系统快照(`GlobalMemoryStatusEx` 可用物理内存、`GetPerformanceInfo` 提交余量)在同一把锁下原子评估——消除"持 CPU 等内存、持内存等 CPU"的部分占有死锁
|
|
179
|
+
- **机会式准入判据**(全部满足才启动):CPU 令牌充足;峰值可能拥挤时距上次授予 ≥ 最小启动间隔(`memory_min_start_interval_s`,默认 1s,错开启动防扎堆);提交余量 ≥ 新任务估算需求 + 提交保留量(`memory_commit_reserve_mb`,默认 2048 MB);可用物理内存 ≥ 物理低水位(`memory_physical_watermark_mb`,默认 2048 MB,独立检查不与需求量挂钩)。提交与物理两种口径分开建模、互不混用
|
|
180
|
+
- **不重复计账**:不再为运行中任务保留完整未来峰值——已占用内存自然体现在系统余量中;未来再次增长导致超额的风险明确接受(允许偶发 OOM,不保证零失败)。实测证明旧的"完整预留 + 快照兜底"策略在 31.8 GiB 机器上把 2/4 worker 并发压到 1
|
|
181
|
+
- 平铺与依赖调度均在提交到线程池前检查准入。暂未获准的就绪用例留在调度队列,后续符合条件的用例可以先运行。调度器在用例结束时或按轮询周期重试,启动间隔即将结束时提前重试
|
|
182
|
+
- 拒绝原因(含关键数值:需求/保留量/余量/水位)来自实际判断路径,记入 `waiter.deny_reason` 与调度日志,供验收归因
|
|
183
|
+
- 物理低水位校验:已知总物理内存时,非零水位必须严格小于总量,否则初始化抛出 `ValueError`,避免永久排队。请降低 `memory_physical_watermark_mb`,或设为 0 禁用该检查。
|
|
184
|
+
- 内存不足排队等待而非降级(CPU 的 10s 降级逻辑不适用内存);需求未知(`None`)或需求加提交保留量超过系统提交上限(结构性不可满足,如 pagefile 过小)时跳过提交检查放行(物理水位与启动间隔仍生效),交由用例自身失败暴露问题,不永久排队
|
|
185
|
+
- Job 内全部后代与启动器共享命令超时期限;管道 EOF 后继续等待组内进程结束,期限耗尽则终止整组并报告超时
|
|
186
|
+
- 排空查询的 PID 数组使用指针宽度;缓冲区不足或列表不完整时扩容重试(每轮最多 8 次)。查询失败抛出 `JobError`,不作为超时;执行器记录警告,保留 `communicate` 已取得的输出和返回码,不重新执行命令,峰值保持未知。此时无法确认后代排空,关闭 Job 仍清理残留进程。
|
|
187
|
+
- 上述参数为 `symtest.json` run 段配置键(CLI 第一版不提供旗标);进程模式不接入资源调度(保持既有行为)
|
|
188
|
+
|
|
189
|
+
仅在存在活动任务且“活动任务估算峰值之和 + 新任务需求 + 提交保留量”大于当前提交余量时,才要求距上次授予达到启动间隔;余量充足或活动任务全部结束时立即放行。该估算可能重复计入已占用内存,只用于保守地触发间隔,不作为硬预留。快照或需求未知且存在活动任务时保守保留间隔。
|
|
190
|
+
|
|
141
191
|
### 4.4 DAG 依赖调度语义
|
|
142
192
|
|
|
143
193
|
- `depends_on` 非空自动切换拓扑模式;无依赖时走零开销 fast path
|
|
@@ -151,12 +201,17 @@ parse_test_cases() # 转换为 List[TestCase](命令路径解析)
|
|
|
151
201
|
|
|
152
202
|
PathResolver 解析(系统命令直通、shell builtin 平台包装、复合命令拆分解析)
|
|
153
203
|
→ 声明产物清理(`execution.outputs` 声明的文件在 subprocess 启动前删除;只允许声明文件,声明目录或 workspace 根一律拒绝;路径 resolve 后必须在 workspace 内,删除失败大声失败记为执行错误;每次 attempt 都执行,`--resume` 跳过的 step 天然不清理)
|
|
154
|
-
→ subprocess 隔离执行(捕获 stdout / stderr / returncode / duration
|
|
204
|
+
→ subprocess 隔离执行(捕获 stdout / stderr / returncode / duration;Windows 测量启用时经 Job Object 以挂起创建→绑定→恢复执行整组进程,捕获进程组提交内存峰值 `PeakJobMemoryUsed`,超时经 `TerminateJobObject` 终止整组,测量失败回退普通 subprocess 路径、峰值保持未知)
|
|
155
205
|
→ 断言校验(return_code / contains / matches / compare_files)
|
|
156
206
|
→ 失败按 `retry_count` 重试
|
|
157
207
|
→ 超时 kill 整个进程组
|
|
158
208
|
→ 返回附带 `next_action_hint` 的结构化结果。
|
|
159
209
|
|
|
210
|
+
进程组内存峰值是**执行事实**(原则 2),随结果可选携带 `peak_memory_bytes` /
|
|
211
|
+
`peak_memory_source`(Windows 提交内存口径,非物理内存峰值;无可测量时字段缺席,
|
|
212
|
+
不用 0 表示未知)。聚合规则:retry 取各 attempt 最大值;sequence 取实际执行步骤的
|
|
213
|
+
最大值(步骤串行,不求和;`--resume` 跳过的步骤不补造数据)。
|
|
214
|
+
|
|
160
215
|
### 4.6 断言与文件比较集成
|
|
161
216
|
|
|
162
217
|
- `compare_files` 是一等断言,经 ComparatorFactory 按类型分发(详见 §6)
|
|
@@ -197,6 +252,16 @@ PathResolver 解析(系统命令直通、shell builtin 平台包装、复合
|
|
|
197
252
|
- 统一返回 `ComparisonResult`(identical / differences / error / error_stats / command_output / channels),支持 text / json / html 渲染
|
|
198
253
|
- 数据泳道插件可通过 `ChannelData.extra_stats` 附带自定义误差指标,存放在独立命名空间(`ChannelResult.extra_stats`),不可覆盖框架规范指标;但 verdict 仍由框架容差持有——需要自定 verdict 的走自主泳道
|
|
199
254
|
|
|
255
|
+
#### 6.1.1 窗口与数值比较语义(文件泳道)
|
|
256
|
+
|
|
257
|
+
- 行列窗口统一 **0-based 闭区间**(`start_line`/`end_line`/`start_column`/`end_column`,end 含端点),断言层负责把用户 1-based 输入转换;CSV 的列窗口按 **CSV 字段**裁剪(不是字符列),H5 的大数据集分块分支同样应用窗口,与内存分支语义一致。差异 position(`line N` / `row N, column M` / `row N`)由泳道基类统一偏移回原始文件坐标
|
|
258
|
+
- H5 标量(0 维)数据集参与数值比较;数据集读取失败记为 `diff_type="error"` 差异并判失败,绝不静默通过
|
|
259
|
+
- `allow_nonfinite` 的布尔类型约束在原始/展开配置 schema 中复用同一定义,比较器构造及共享数值核心也检查 Python API 输入,禁止依赖真值转换。CSV 文本快速路径对所有含指数、NaN/Inf 提示或长度不少于 309 的单元格实际解析,以覆盖长尾数和带下划线的溢出写法;是否启用误差统计不影响判定。数据泳道(含 `script_extract`)的覆盖顺序为逐通道 → `default_channel` → 比较器参数 → `false`。
|
|
260
|
+
- 共享数值核心 `compare_numeric` 逐元素保留整数类型,覆盖完整 int64 / uint64 范围及整数、浮点混合序列;整数差值使用 Python 整数避免溢出,整数与浮点数配对时按该浮点数实际表示的值计算差值。判定前不把整数转成 float64,也不因其他单元格的类型或幅值回退浮点通路。纯浮点数组仍走 NumPy 向量化比较。容差与报告中的误差幅值统计使用浮点数;调用者已转成浮点数组而丢失的精度无法恢复。CSV 数值单元格整数优先解析,H5 / 数据泳道可直接传整数数组
|
|
261
|
+
- **非有限值默认拒绝**:任意一侧为 NaN 或 ±Inf 的单元格判为不匹配(差异 `diff_type="non_finite_value"`)——求解器输出出现 NaN/Inf 通常意味着求解失败,"结果与基准一致"不能推出"结果有效"。需要接受非有限值时显式设置 `allow_nonfinite=true`(CSV/H5 比较器参数、数据泳道比较器参数及 per-channel 覆盖),仅恢复 `NaN==NaN`、同号 `±Inf` 相等的旧语义;反号 Inf 仍然是不匹配。该规则在共享数值核心实施,CSV(含流式/内存文本快速路径与 `1e999` 溢出文本)、H5(含大数据集分块分支)、数据泳道三路一致;`data_filter` 不能提前排除非有限单元格,被过滤条件排除的 NaN 仍会被强制纳入比较并判失败
|
|
262
|
+
- CSV 误差统计累计用于 verdict 的逐行数值比较结果,不汇总原始数值后重新比较;比较走流式逐行路径(覆写 `compare_files`),行窗口按记录索引施加,行数不匹配在两侧流读取耗尽后按窗口内记录数判定和报告,窗口外的增删行不影响结果;起始记录索引大于等于任一文件的总记录数时返回越界错误(包括空文件)。内存与文件大小无关(O(单行));直接调用 `read_content`/`compare_content` 的 Python API 保留全量内存路径,两者共享逐行判定逻辑
|
|
263
|
+
- `--error-analysis` 误差统计覆盖参与比较的全部数值单元格,含 H5 分块大数据集(启用统计时不因首个差异提前返回)
|
|
264
|
+
|
|
200
265
|
### 6.2 通道协议(数据泳道)
|
|
201
266
|
|
|
202
267
|
- 通道判定:`identical = all(channels.passed)`;差异 position 带通道前缀(`channel S33`);`error_stats` 按通道名嵌套
|
|
@@ -281,6 +346,12 @@ JSON/YAML 配置,学习成本更低且无交互界面维护负担。
|
|
|
281
346
|
| 项目级默认配置(`.symtest/symtest.json`) | 常用运行参数(并行、误差分析、依赖展开、报告路径)项目内固化,`symtest run` 免重复输入。三级优先级(CLI > 项目配置 > 内置默认)靠 tri-state 布尔项实现(argparse 默认 `None`,`--no-xxx` 显式关闭);未知键/坏 JSON 宽容处理只警告——配置是纯加分项,不阻断运行。替代各仓库自建入口脚本保存默认参数的用法 |
|
|
282
347
|
| `--defaults FILE` 显式默认参数文件 | 同一 workspace 需要多套默认参数(如回归 vs 验证)时免建项目 runner。显式文件**完全替代** `.symtest/symtest.json`(不叠加合并,防止验证配置漏写键时静默继承回归设置),并切换为**严格校验**(缺失/坏 JSON/未知键/类型错报错退出)——显式指定即用户意图,静默回退到另一套设置比报错更危险。默认入口保持宽容语义不变,与 `--no-config` 互斥 |
|
|
283
348
|
| Logging 统一化 | 通过 `logging` 模块集中管理,CLI 入口激活控制台输出,库用户按需启用 |
|
|
349
|
+
| Windows Job Object 测量进程组峰值 | 挂起创建→绑定 Job→恢复执行消除后代逃逸竞态;峰值由操作系统持续维护,无需采样即可捕捉短暂尖峰;`PeakJobMemoryUsed` 为提交内存口径,如实命名为 `peak_memory_source=windows_job_commit`,不冒充物理内存峰值 |
|
|
350
|
+
| CPU+内存联合原子准入 | 两个独立信号量会产生"持 CPU 等内存、持内存等 CPU"的部分占有死锁;联合池在同一把锁下原子评估池令牌 + 系统快照(物理可用与提交余量分别检查,二者防护目标不同) |
|
|
351
|
+
| 机会式内存准入(不做完整峰值预留) | 旧的"系统余量须覆盖运行中任务的完整预留 + 新请求"会重复计入已分配内存(实测把 2/4 worker 并发压到 1),且把提交峰值误用于物理内存检查。机会式准入只检查新任务自身需求 + 保留量;已占用内存由系统余量自然体现;峰值可能拥挤时授予间保持最小启动间隔错开扎堆;允许偶发 OOM,不保证零失败 |
|
|
352
|
+
| 内存排队而非降级 | CPU 令牌超时降级到 1 核是吞吐启发式;内存降级启动正是并行 OOM 失败的来源,故内存不足持续等待(周期唤醒重评外部内存变化),结构性不可满足(需求加提交保留量超提交上限)才跳过检查放行 |
|
|
353
|
+
| 内存历史用最大值而非平均 | 峰值口径天然只增,偶发高峰被平均稀释后会在下次调度再次 OOM;估算加安全系数(默认 1.2,可配) |
|
|
354
|
+
| 内存测量失败回退普通路径 | 测量是加分项不是验收条件:Job 后端失败/非 Windows/进程模式时峰值保持未知(None,不用 0 伪装),执行与判定语义完全不变 |
|
|
284
355
|
| 控制台 log/report 通道分离 | 控制台(stderr logging)只承载进度与摘要日志;报告仅在显式 `--output-format text/json/html` 时走 stdout(可重定向落盘),细节经 `--text-report`/`--html-report`/`--junit-xml` 写文件。修复原 `print_report` 把整份文本报告经 `logger.info` 重放到终端的通道混流——`--error-analysis-all` 下逐用例 error_stats 会淹没 pass/failed 摘要 |
|
|
285
356
|
|
|
286
357
|
---
|
|
@@ -53,7 +53,7 @@ Responsibilities by package (file-level details and public APIs live in source):
|
|
|
53
53
|
|---|---|
|
|
54
54
|
| `cli.py` / `commands/` | Sub-command entry points, argument assembly, logging activation |
|
|
55
55
|
| `core/` | TestCase model, assertion engine, single-test execution, Runner bases (sequential / parallel / DAG), `.symtest` state stores, Setup plugin system |
|
|
56
|
-
| `config/` | Config IO, JSON Schema validation (draft 2020-12), import expansion, extends inheritance, variable & placeholder substitution |
|
|
56
|
+
| `config/` | Config IO, shared preparation pipeline (`prepared.py`), dual-form JSON Schema contract & validation (draft 2020-12, `config_schema.py`), import expansion, extends inheritance, variable & placeholder substitution |
|
|
57
57
|
| `runners/` | Thin wrapper runners: Config/JSON/YAML × sequential/parallel |
|
|
58
58
|
| `file_comparator/` | Comparator family + factory + workspace plugin discovery (see §6) |
|
|
59
59
|
| `utils/` | Path resolution, report generation, JUnit XML output, project-level default configuration (`.symtest/symtest.json`) |
|
|
@@ -71,27 +71,66 @@ Responsibilities by package (file-level details and public APIs live in source):
|
|
|
71
71
|
|
|
72
72
|
## 3. Config Pipeline
|
|
73
73
|
|
|
74
|
-
|
|
74
|
+
Raw templates and heirs may provide partial `execution` dictionaries. Their
|
|
75
|
+
schema reuses the complete execution field constraints and defers only the
|
|
76
|
+
required `command/args` checks. Supplied steps remain complete because lists
|
|
77
|
+
are replaced as a whole. `load_config(..., workspace=...)` forwards the workspace
|
|
78
|
+
to preparation, and `find` passes its CLI workspace explicitly. Imported file
|
|
79
|
+
read errors, including YAML parser errors, are normalized at the file boundary
|
|
80
|
+
into diagnostics carrying the failing file and its referring file.
|
|
81
|
+
|
|
82
|
+
The single source of truth for the configuration contract is
|
|
83
|
+
`config/config_schema.py` (JSON Schema draft 2020-12, two variants):
|
|
84
|
+
|
|
85
|
+
- **Raw form** (`CONFIG_SCHEMA`): original config files as written by
|
|
86
|
+
users / AI agents. `abstract` templates and `extends` heirs may omit
|
|
87
|
+
required execution fields — completeness is enforced after expansion.
|
|
88
|
+
`symtest schema` exports this variant.
|
|
89
|
+
- **Expanded form** (`EXPANDED_CONFIG_SCHEMA`): the effective config after
|
|
90
|
+
import / extends / variables have all been resolved. Every executable
|
|
91
|
+
case must be complete.
|
|
92
|
+
|
|
93
|
+
The three entry points (`validate` / `run` / `find`) share one preparation
|
|
94
|
+
pipeline, `config/prepared.py:prepare_config()`; structural failures stop
|
|
95
|
+
processing of the affected input (later stages never see malformed dicts):
|
|
75
96
|
|
|
76
97
|
```
|
|
77
98
|
raw JSON/JSONC/YAML file (.jsonc is preprocessed by config/jsonc.py: comments and trailing commas are stripped)
|
|
78
99
|
│
|
|
79
100
|
▼
|
|
80
|
-
|
|
101
|
+
raw-form schema validation # every loaded file (incl. imported sub-files):
|
|
102
|
+
# field names / types / value ranges /
|
|
103
|
+
# execution-form exclusivity / unknown fields
|
|
81
104
|
│
|
|
82
105
|
▼
|
|
83
|
-
|
|
106
|
+
expand_imports() # Recursively expand import references (merge setup, inject tags)
|
|
84
107
|
│
|
|
85
108
|
▼
|
|
86
|
-
|
|
109
|
+
duplicate-name check # extends references must be unambiguous
|
|
87
110
|
│
|
|
88
111
|
▼
|
|
89
|
-
|
|
112
|
+
resolve_inheritance() # Resolve extends chains (deep-merge, remove abstract)
|
|
90
113
|
│
|
|
91
114
|
▼
|
|
92
|
-
|
|
115
|
+
apply_variables() # Inject --var global variables + case-level variables,
|
|
116
|
+
# recursively replace {placeholder} tokens
|
|
117
|
+
│
|
|
118
|
+
▼
|
|
119
|
+
expanded-form validation # every executable case must be complete after expansion
|
|
120
|
+
│
|
|
121
|
+
▼
|
|
122
|
+
semantic checks # error-level: depends_on graph (existence / self-ref /
|
|
123
|
+
# cycles), outputs path boundaries; warning-level:
|
|
124
|
+
# command executability, baseline existence, outputs conflicts
|
|
125
|
+
│
|
|
126
|
+
▼
|
|
127
|
+
parse_test_cases() # Convert to List[TestCase] (command path resolution)
|
|
93
128
|
```
|
|
94
129
|
|
|
130
|
+
Adding a new ordinary config field now only requires defining its validity in
|
|
131
|
+
the schema and implementing its conversion in the parser — `validate` picks up
|
|
132
|
+
the check automatically; no separate field-rule list is maintained.
|
|
133
|
+
|
|
95
134
|
### 3.1 Import Expansion (`import_expander.py`)
|
|
96
135
|
|
|
97
136
|
Main config files reference sub-config files via `"import"`:
|
|
@@ -112,12 +151,24 @@ The `extends` field enables test-case template inheritance:
|
|
|
112
151
|
- `variables` collected along the extends chain are substituted at resolve time
|
|
113
152
|
- Circular extends detection
|
|
114
153
|
|
|
115
|
-
### 3.3 Config Validation (`config_io.py`)
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
154
|
+
### 3.3 Config Validation & Shared Preparation Pipeline (`prepared.py` / `config_io.py`)
|
|
155
|
+
|
|
156
|
+
`validate_config()` delegates to `prepare_config()`; the `run` loading stage
|
|
157
|
+
and `find` (via `load_config()`) go through the same pipeline. An invalid
|
|
158
|
+
config yields identical errors from `validate` and `run`, and `run` exits
|
|
159
|
+
before executing any command. Diagnostics carry the file path and field path
|
|
160
|
+
(jsonschema `json_path`); errors inside imported sub-files are localized to
|
|
161
|
+
the exact file and field.
|
|
162
|
+
|
|
163
|
+
- Error-level (affects `valid`): JSON/YAML syntax; raw/expanded schema checks
|
|
164
|
+
(required fields, types, value ranges, execution-form exclusivity, unknown
|
|
165
|
+
fields); import target existence; circular imports; duplicate case names;
|
|
166
|
+
extends target existence; circular inheritance; post-expansion case
|
|
167
|
+
completeness; `outputs` path boundaries; depends_on target existence /
|
|
168
|
+
self-reference / cycles
|
|
169
|
+
- Warning-level (does not affect `valid`): `command` executability (PATH
|
|
170
|
+
lookup), `compare_files` baseline file existence, multiple cases declaring
|
|
171
|
+
the same outputs path without depends_on
|
|
121
172
|
|
|
122
173
|
## 4. Execution Semantics
|
|
123
174
|
|
|
@@ -130,7 +181,7 @@ The `symtest validate` subcommand checks configuration without running tests:
|
|
|
130
181
|
- JSON/YAML runners differ only by injected config_loader; common logic lives in the generic sequential / parallel runners
|
|
131
182
|
- xfail: when `expected_failure=True`, `passed → xpassed` (unexpected pass, counted as a suite failure); any non-passed status → `xfailed` (expected failure, not counted)
|
|
132
183
|
- JUnit XML status mapping: `xfailed → <skipped>`, `xpassed → <failure>`, `timeout → <error>`, `failed` split into `<failure>` / `<error>` by message type
|
|
133
|
-
- History: cumulative average update; regression is checked against the prior average before writing; `--update-history` clears
|
|
184
|
+
- History: duration uses cumulative average update; regression is checked against the prior average before writing; memory peaks are recorded independently (`last_peak_memory_bytes` / `max_peak_memory_bytes` / `peak_memory_count` / `peak_memory_source`, bytes) for any run with a valid measurement (including failed / timeout), scheduling estimates use the historical maximum; `--update-history` clears the whole record (duration + memory)
|
|
134
185
|
- `--last-failed`: each run overwrites only the statuses of executed cases; subset runs never lose states of unexecuted cases
|
|
135
186
|
|
|
136
187
|
### 4.2 Two Case Modes
|
|
@@ -142,12 +193,28 @@ JSON Schema; it is not restated here.
|
|
|
142
193
|
|
|
143
194
|
### 4.3 Parallelism and Resource Scheduling
|
|
144
195
|
|
|
145
|
-
- LPT strategy: long tasks first; with history enabled, historical `avg_duration` takes precedence over declared `estimated_time`
|
|
196
|
+
- LPT strategy: long tasks first; with history enabled, historical `avg_duration` takes precedence over declared `estimated_time` (entries with memory-only records and no duration fields are tolerated, treated as 0)
|
|
146
197
|
- `AtomicSemaphore` resource pool: `safe_capacity = max(1, cpu_count − 2)`; per-case acquire/release by `cpu_cores`
|
|
147
198
|
- Relative CPU cores assigned proportionally by weight; auto-injects `OMP_NUM_THREADS` / `MKL_NUM_THREADS` / `NPROC`
|
|
148
199
|
- Environment variable precedence: `os.environ` < scheduler injection < case-level env (via subprocess, never mutating global `os.environ`)
|
|
149
200
|
- Thread mode shares memory with result/print locks; process mode isolates via process workers; sequential fallback available
|
|
150
201
|
|
|
202
|
+
**Windows memory-aware scheduling — opportunistic admission** (enabled for thread mode on Windows when `--history-dir` is set or `min_memory_mb` is declared; otherwise the original CPU-only path is kept unchanged):
|
|
203
|
+
|
|
204
|
+
- Demand estimate priority: explicit `min_memory_mb` > historical max peak × safety factor (default 1.2, configurable via `memory_margin`) > configurable default demand (`memory_default_demand_mb`, default 4096 MB); no more whole-pool exclusive runs
|
|
205
|
+
- `JointResourceManager` joint pool: CPU tokens + a system snapshot (`GlobalMemoryStatusEx` available physical memory, `GetPerformanceInfo` commit margin) are evaluated atomically under a single lock — eliminating the partial-holding deadlock of "holding CPU while waiting for memory and vice versa"
|
|
206
|
+
- **Admission criteria** (all must hold to start): CPU tokens suffice; under potential peak crowding, at least the minimum startup interval (`memory_min_start_interval_s`, default 1s) has elapsed since the previous grant (staggered starts, avoiding thundering herds that all see the same headroom); commit margin ≥ the new task's estimated demand + commit reserve (`memory_commit_reserve_mb`, default 2048 MB); available physical memory ≥ the physical watermark (`memory_physical_watermark_mb`, default 2048 MB, an independent pressure check not tied to the demand). The commit and physical budgets are modelled separately and never mixed
|
|
207
|
+
- **No double counting**: full future peaks are no longer reserved for running tasks — memory already in use shows up naturally in the system headroom; the residual risk of a running task growing again is explicitly accepted (occasional OOM allowed, zero-failure not guaranteed). Measurements proved the old "full reservations + snapshot backstop" policy squeezed 2/4-worker concurrency down to 1 on a 31.8 GiB machine
|
|
208
|
+
- Both flat and dependency scheduling check admission before submitting cases to the thread pool. Denied ready cases stay in the scheduler queue, and later eligible cases can run first. The scheduler retries on case completion or at the polling interval, with earlier retries when a startup interval expires
|
|
209
|
+
- Denial reasons (with key numbers: demand / reserve / headroom / watermark) come from the actual decision path and are stored on `waiter.deny_reason` plus the scheduler log for acceptance attribution
|
|
210
|
+
- Physical watermark validation: when total physical memory is known, a nonzero watermark must be strictly below it; otherwise initialization raises `ValueError` instead of waiting forever. Lower `memory_physical_watermark_mb`, or set it to 0 to disable this check.
|
|
211
|
+
- Memory shortage queues instead of downgrading (the CPU 10s-downgrade heuristic does not apply to memory); unknown demand (`None`) or demand plus commit reserve beyond the system commit limit (structurally unsatisfiable, e.g. a small pagefile) skip the commit check and run (physical watermark and startup interval still apply), leaving the problem to the case's own failure rather than queueing forever
|
|
212
|
+
- All descendants in a Job share the launcher's command deadline. After pipe EOF, execution still waits for the group to finish; reaching the deadline terminates the group and reports a timeout.
|
|
213
|
+
- Drain queries use pointer-sized PID entries and resize insufficient buffers or incomplete lists (at most 8 retries per poll). Query failures raise `JobError`, not a timeout; the executor logs a warning, preserves the output and return code already obtained from `communicate`, does not rerun the command, and leaves the peak unknown. Descendant completion cannot be confirmed in this case; closing the Job still cleans up remaining processes.
|
|
214
|
+
- These parameters are `symtest.json` run-section config keys (no CLI flags in the first version); process mode does not participate in resource scheduling (unchanged behavior)
|
|
215
|
+
|
|
216
|
+
The startup interval applies only while tasks are active and their summed estimated peaks plus the new demand and commit reserve exceed current commit headroom. Ample headroom or an empty active set permits immediate admission. This conservative signal may double-count allocated memory; it triggers spacing, never a hard reservation. With active tasks and unknown demand or headroom, spacing is retained conservatively.
|
|
217
|
+
|
|
151
218
|
### 4.4 DAG Dependency Scheduling Semantics
|
|
152
219
|
|
|
153
220
|
- Non-empty `depends_on` automatically switches to topological mode; no deps walks a zero-overhead fast path
|
|
@@ -166,10 +233,18 @@ workspace root are always rejected; resolved
|
|
|
166
233
|
paths must stay inside the workspace, deletion failure fails loudly as an execution
|
|
167
234
|
error; runs on every attempt, and steps skipped by `--resume` are naturally not
|
|
168
235
|
cleaned) → subprocess-isolated execution (captures
|
|
169
|
-
stdout / stderr / returncode / duration) → assertions (return_code / contains /
|
|
236
|
+
stdout / stderr / returncode / duration; when Windows measurement is enabled, the process group runs inside a Job Object created suspended → assigned → resumed, capturing the group's commit-memory peak `PeakJobMemoryUsed`; on timeout `TerminateJobObject` kills the whole group; measurement failure falls back to the plain subprocess path with the peak left unknown) → assertions (return_code / contains /
|
|
170
237
|
matches / compare_files) → retries on failure up to `retry_count` → kills the
|
|
171
238
|
whole process group on timeout → structured result with `next_action_hint`.
|
|
172
239
|
|
|
240
|
+
The process-group memory peak is an **execution fact** (Principle 2), optionally
|
|
241
|
+
carried on results as `peak_memory_bytes` / `peak_memory_source` (Windows
|
|
242
|
+
commit-memory basis, NOT physical-memory peak; fields are absent when no valid
|
|
243
|
+
measurement exists — never 0-for-unknown). Aggregation: retry takes the maximum
|
|
244
|
+
across attempts; a sequence takes the maximum across actually-executed steps
|
|
245
|
+
(steps run serially, no summation; steps skipped by `--resume` contribute no
|
|
246
|
+
fabricated data).
|
|
247
|
+
|
|
173
248
|
### 4.6 Assertions and File Comparison Integration
|
|
174
249
|
|
|
175
250
|
- `compare_files` is a first-class assertion dispatched via ComparatorFactory (see §6)
|
|
@@ -181,7 +256,7 @@ whole process group on timeout → structured result with `next_action_hint`.
|
|
|
181
256
|
| State | Content | Update timing / semantics |
|
|
182
257
|
|---|---|---|
|
|
183
258
|
| Project defaults `symtest.json` | `run` group run options + `report` group report paths | Read once at run start (CLI > project config > built-in defaults); read-only, never updated during a run |
|
|
184
|
-
| History | per-case `avg_duration` / `last_duration` / `run_count` |
|
|
259
|
+
| History | per-case `avg_duration` / `last_duration` / `run_count` + optional memory fields (`last_peak_memory_bytes` / `max_peak_memory_bytes` / `peak_memory_count` / `peak_memory_source`) | Duration: cumulative average after runs, regression-checked before writing (passed cases only); memory: recorded for any run with a valid measurement, scheduling estimates use the historical max |
|
|
185
260
|
| `last_run.json` | case → last status | Overwrites executed cases; unexecuted retain old status |
|
|
186
261
|
| `sequence_state/<case>.json` | SHA-256 config hash (steps + case expected), set of passed steps | Saved after each passing step; cleaned up after full pass |
|
|
187
262
|
| `sequence_state/cache/*.log` | Step output cache | Kept in sync; spliced back on resume |
|
|
@@ -199,6 +274,16 @@ guarantees they are unmodified.
|
|
|
199
274
|
- h5 targets scientific datasets; binary uses stream chunking + LCS similarity; script delegates to an external program
|
|
200
275
|
- All return a ComparisonResult (identical / differences / error / script command_output), renderable as text / json / html; supports row/column windowing before comparison
|
|
201
276
|
|
|
277
|
+
#### 6.1.1 Window and numeric comparison semantics (file lane)
|
|
278
|
+
|
|
279
|
+
- Row/column windows are uniformly **0-based, end-inclusive** (`start_line`/`end_line`/`start_column`/`end_column`); the assertion layer converts the user's 1-based input. CSV column windows select **CSV fields** (not character columns); the H5 chunked large-dataset branch applies the same window as the in-memory branch. Difference positions (`line N` / `row N, column M` / `row N`) are offset back to original file coordinates by the lane base class
|
|
280
|
+
- H5 scalar (0-d) datasets participate in numeric comparison; a dataset read failure is recorded as a `diff_type="error"` difference and fails the comparison — never a silent pass
|
|
281
|
+
- The raw and expanded schemas share the boolean constraint for `allow_nonfinite`; comparator constructors and the shared numeric core also check Python API inputs without truthiness conversion. The CSV text fast path parses every cell containing an exponent or NaN/Inf hint, or at least 309 characters, covering overflow from long mantissas and underscore spellings; enabling error statistics does not change the verdict. Data-lane precedence, including `script_extract`, is per-channel → `default_channel` → comparator parameter → `false`.
|
|
282
|
+
- The shared numeric core `compare_numeric` preserves integer types per element, including the full int64 / uint64 ranges and mixed integer/float sequences. Integer differences use Python integers to avoid overflow; integer/float pairs use the float's actual represented value when computing the difference. Integers are not converted to float64 before verdict calculation, and unrelated cells cannot force a floating fallback. Pure floating arrays retain NumPy vectorized comparison. Tolerances and reported error magnitudes use floating-point numbers; precision already lost in caller-created floating arrays cannot be recovered. CSV cells parse integers first; H5 / the data lane can supply integer arrays directly
|
|
283
|
+
- **Non-finite values are rejected by default**: any cell where either side is NaN or ±Inf is a mismatch (difference `diff_type="non_finite_value"`) — NaN/Inf in solver output usually indicates a failed solve, and "matches the baseline" must not be conflated with "is a valid result". Set `allow_nonfinite=true` explicitly (CSV/H5 comparator parameter, data-lane comparator parameter with per-channel override) to restore the legacy semantics where `NaN == NaN` and same-sign `±Inf` count as equal; opposite-sign infinities remain mismatches. The rule lives in the shared numeric core and applies uniformly across CSV (including the streaming/in-memory text fast paths and `1e999` overflow text), H5 (including the chunked large-dataset branch), and the data lane; a `data_filter` can never pre-exclude non-finite cells — NaN dropped by a filter condition is still force-compared and fails
|
|
284
|
+
- CSV error statistics accumulate the same per-row numeric comparisons used for the verdict, without collecting and recomparing raw numeric values. Comparison streams record by record (compare_files override): the row window applies by record index, and row-count mismatches are determined and reported using record counts inside the window once both streams are drained. Added or removed records outside the window do not affect the verdict. A starting record index greater than or equal to either file's total record count returns an out-of-range error (including empty files). Memory is independent of file size (O(one row)). The Python API (read_content/compare_content) keeps the in-memory path for direct callers; both paths share the same per-row verdict logic
|
|
285
|
+
- `--error-analysis` statistics cover all compared numeric cells, including H5 chunked large datasets (no early return on the first difference when stats are requested)
|
|
286
|
+
|
|
202
287
|
### 6.2 Factory and Plugin Discovery
|
|
203
288
|
|
|
204
289
|
- `file_type` values: `text` / `json` / `csv` / `xml` / `h5` / `binary` / `script`; factory dispatches by type, supports dynamic registration and global reset (for tests)
|
|
@@ -248,8 +333,7 @@ no interactive UI maintenance burden.
|
|
|
248
333
|
| Semaphore-based CPU core management | More fine-grained than thread pool worker count; allows different cases to declare different core requirements |
|
|
249
334
|
| LPT scheduling strategy | Long tasks start first, reducing tail latency; prioritizes `.symtest` historical data |
|
|
250
335
|
| Cumulative average history update | Simple and intuitive; single anomalies are naturally diluted over many runs |
|
|
251
|
-
| Regression check before update | Compare against old average first, then update; ensures comparison is against the "historical baseline" |
|
|
252
|
-
| `.symtest/` directory | Non-intrusive to the user's directory view; JSON format for easy debugging; state files centrally managed |
|
|
336
|
+
| Regression check before update | Compare against old average first, then update; ensures comparison is against the "historical baseline" || `.symtest/` directory | Non-intrusive to the user's directory view; JSON format for easy debugging; state files centrally managed |
|
|
253
337
|
| Environment variable injection | Scientific computing solvers often ignore Python-level thread control |
|
|
254
338
|
| Comparator factory + plugin discovery | Creates comparators by file type; workspace `comparators/` directory for auto-discovered plugins |
|
|
255
339
|
| subprocess isolated execution | Each test case runs in an independent subprocess, ensuring tests don't affect each other |
|
|
@@ -265,6 +349,12 @@ no interactive UI maintenance burden.
|
|
|
265
349
|
| JUnit XML output | Compatible with GitLab CI / Jenkins / CircleCI and other major CI system test report formats |
|
|
266
350
|
| Project-level default configuration (`.symtest/symtest.json`) | Frequently used run options (parallel, error analysis, dependency expansion, report paths) are stored per project so `symtest run` needs no repeated input. Three-level precedence (CLI > project config > built-in defaults) is implemented with tri-state booleans (argparse defaults to `None`; `--no-xxx` turns a flag off explicitly); unknown keys and bad JSON are handled tolerantly with a warning only — the config is a pure bonus and never blocks a run. Replaces per-repo entry scripts whose only job was storing default arguments |
|
|
267
351
|
| Console log/report channel separation | The console (stderr logging) carries progress and summary logs only. Reports reach stdout solely via an explicit `--output-format text/json/html` (redirectable to a file), with full details written to disk via `--text-report`/`--html-report`/`--junit-xml`. Fixes the channel confusion where the former `print_report` replayed the whole text report through `logger.info` — with `--error-analysis-all` the per-case error_stats flooded the terminal and buried the pass/failed summary |
|
|
352
|
+
| Windows Job Object measures process-group peaks | Create-suspended → assign → resume eliminates the descendant-escape race; the OS maintains the peak continuously, catching short spikes without sampling; `PeakJobMemoryUsed` is commit memory, honestly named `peak_memory_source=windows_job_commit`, never presented as a physical-memory peak |
|
|
353
|
+
| Joint atomic CPU+memory admission | Two independent semaphores allow a partial-holding deadlock ("holding CPU while waiting for memory and vice versa"); the joint pool evaluates pool tokens + system snapshot atomically under one lock (physical availability and commit margin are checked separately — they guard different failure modes) |
|
|
354
|
+
| Opportunistic memory admission (no full peak reservations) | The old policy requiring system headroom to cover all active reservations plus the new request double-counted allocated memory (measured to squeeze 2/4-worker concurrency to 1) and misused commit peaks for the physical-memory check. Opportunistic admission checks only the new task's own demand + reserve; memory in use shows up naturally in the system headroom; a minimum startup interval staggers grants only under potential peak crowding; occasional OOM is accepted, zero-failure is not guaranteed |
|
|
355
|
+
| Memory queues instead of downgrading | The CPU token timeout-downgrade is a throughput heuristic; downgraded memory launch is precisely the source of parallel OOM failures, so memory shortage waits indefinitely (periodic wake-ups re-evaluate external memory changes); only structurally unsatisfiable requests (demand plus commit reserve beyond the commit limit) skip the check and run |
|
|
356
|
+
| Memory history uses the maximum, not the average | Peaks are naturally monotone; an occasional spike diluted by averaging would OOM again at the next scheduling; estimates add a safety factor (default 1.2, configurable) |
|
|
357
|
+
| Memory measurement failure falls back to the plain path | Measurement is a bonus, not an acceptance criterion: on backend failure / non-Windows / process mode the peak stays unknown (None, never 0-for-unknown) and execution and verdict semantics are unchanged |
|
|
268
358
|
|
|
269
359
|
---
|
|
270
360
|
|