symtest-cli 1.5.5__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.5/src/symtest_cli.egg-info → symtest_cli-1.6.0}/PKG-INFO +15 -5
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/README.md +14 -4
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/docs/design.md +30 -3
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/docs/design_en.md +35 -6
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/docs/user_manual.md +68 -3
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/docs/user_manual_en.md +92 -3
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/pyproject.toml +1 -1
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/SKILL.md +17 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/references/user_manual.md +92 -3
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/run.py +15 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/base_runner.py +20 -1
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/execution/executor.py +76 -17
- {symtest_cli-1.5.5 → 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.5 → symtest_cli-1.6.0}/src/symtest/core/history_store.py +41 -4
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/orchestration/sequence.py +13 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/orchestration/single.py +20 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/src/symtest/core/types.py +6 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/parallel_config_runner.py +242 -11
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/project_config.py +22 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0/src/symtest_cli.egg-info}/PKG-INFO +15 -5
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/SOURCES.txt +11 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/README.md +13 -0
- {symtest_cli-1.5.5 → 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/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.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_preparation.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_h5_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_find.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.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.5 → 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.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/utils/test_project_config.py +80 -0
- symtest_cli-1.5.5/tests/integration/parallel/__pycache__/test_parallel_runner.cpython-312-pytest-9.0.3.pyc +0 -0
- symtest_cli-1.5.5/tests/integration/parallel/test_parallel_runner.py +0 -208
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/LICENSE +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/MANIFEST.in +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/setup.cfg +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/full_runner_example.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/extract_channels_script.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/my_analysis_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/my_channel_extractor.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_golden_file.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_simple.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_simple.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/assets/templates/test_cases_steps.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/skill/references/field_reference.md +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/cli.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/find.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/migrate.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/schema.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/commands/validate.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/config_io.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/config_schema.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/import_expander.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/inheritance_expander.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/jsonc.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/migrate.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/normalize.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/config/prepared.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/config_loader.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/execution/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/last_run_store.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/orchestration/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/orchestration/accept.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/process_worker.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/sequence_state.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/setup.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/test_case.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/validation/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/validation/assertions.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/validation/result.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/core/validation/validator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/base_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/binary_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/csv_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/extractor_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/factory.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/file_comparator_base.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/h5_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/json_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/numeric_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/result.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/script_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/script_extract_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/text_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/file_comparator/xml_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/logging_config.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/reporting/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/reporting/diagnosis.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/config_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/json_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/parallel_json_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/parallel_yaml_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/runners/yaml_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/html_report.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/junit_xml_writer.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/path_resolver.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest/utils/report_generator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/dependency_links.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/entry_points.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/requires.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/src/symtest_cli.egg-info/top_level.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-313.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/__init__.cpython-39.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/conftest.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-313.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/run_all.cpython-39.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/__pycache__/test_setup_module.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/conftest.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/demos/h5_filter_demo.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/demos/manual_report_example.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/demos/perf_parallel.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__init__.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-313.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/__init__.cpython-39.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/__pycache__/test_user_flows.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/e2e/test_user_flows.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/circular_config_a.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/circular_config_b.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/hourglass_stdout_mismatch.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/hourglass_stdout_sample.txt +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/inheritance_base.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/inheritance_chain.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/inheritance_circular.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/main_config.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/circular_config_a.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/circular_config_b.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_base.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_chain.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/inheritance_circular.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/main_config.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/missing_fields.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/setup_main.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/setup_sub.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_golden_file.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_simple.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_simple.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/skill_test_cases_steps.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/sub_json_tests.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/sub_text_tests.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_cases1.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_with_setup.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/migration/v1/test_with_setup.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/missing_fields.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/mock_fail_script.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/mock_pass_script.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/setup_main.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/setup_sub.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/sub_json_tests.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/sub_text_tests.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/test_cases.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/test_cases.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/test_cases1.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/test_with_setup.json +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/fixtures/test_with_setup.yaml +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_history_feature.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/__pycache__/test_sequence.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_binary_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_csv_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_h5_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_json_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_text_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/file_compare/test_xml_compare.py +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/integration/parallel/test_depends_on.py +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/integration/path_handling/test_spaces_in_paths.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/test_history_feature.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/test_new_cli_features.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/test_real_command_execution.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/integration/test_sequence.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/run_all.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_binary_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_cli.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_config_io.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_h5_comparator.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_h5_comparator.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_import_expander.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_inheritance_expander.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_jsonc.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_migrate.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_migrate.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_result.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/__pycache__/test_run_all.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/commands/__pycache__/test_find.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/commands/test_compare_command.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/commands/test_find.py +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_assertions.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_execution.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_setup.cpython-39-pytest-8.3.4.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-312-pytest-7.4.4.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-312-pytest-9.0.3.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/__pycache__/test_xfail.cpython-313-pytest-9.0.2.pyc +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_architecture_guard.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_assertions.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_case_env.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_config_loader.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_config_loader_new_features.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_execution.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_execution_new_features.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_last_run_store.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_model_v2.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_orchestration_accept.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_outputs_cleanup.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_parallel_results_echo.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_process_worker.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_sequence_state.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_setup.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_validation_error.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/core/test_xfail.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/__pycache__/__init__.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_error_analysis.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_extractor_channels.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_hourglass_tangent_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_numeric_compare.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_numeric_parity.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_plugin_lifecycle.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_script_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_script_extract.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/file_comparator/test_workspace_plugins.py +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/runners/__pycache__/test_json_yaml_runner.cpython-312.pyc +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/runners/test_json_yaml_runner.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/runners/test_test_case_filter.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/runners/test_test_case_tag_filter.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/runners/test_with_deps.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_binary_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_cli.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_config_io.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_config_preparation.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_h5_comparator.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_import_expander.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_inheritance_expander.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_jsonc.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_migrate.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_result.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/test_run_all.py +0 -0
- {symtest_cli-1.5.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → 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.5 → symtest_cli-1.6.0}/tests/unit/utils/test_html_report.py +0 -0
- {symtest_cli-1.5.5 → symtest_cli-1.6.0}/tests/unit/utils/test_junit_xml_writer.py +0 -0
- {symtest_cli-1.5.5 → 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
|
|
@@ -214,11 +214,21 @@ symtest run test_cases.json --parallel --workers 4
|
|
|
214
214
|
symtest run test_cases.json --parallel --execution-mode process
|
|
215
215
|
```
|
|
216
216
|
|
|
217
|
-
Thread mode
|
|
217
|
+
Thread mode supports CPU-token allocation, solver thread environment
|
|
218
218
|
variables, and longest-processing-time-first scheduling using estimates or
|
|
219
|
-
runtime history.
|
|
220
|
-
|
|
221
|
-
|
|
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.
|
|
222
232
|
|
|
223
233
|
## CI and reports
|
|
224
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
|
|
|
@@ -155,7 +155,7 @@ raw 形态的模板和继承用例允许局部 `execution` 字典,复用完整
|
|
|
155
155
|
- JSON/YAML Runner 仅注入不同的 config_loader,通用逻辑统一在顺序 / 并行通用运行器中
|
|
156
156
|
- xfail:`expected_failure=True` 时 `passed → xpassed`(意外通过,计入失败);任意非 passed → `xfailed`(预期失败,不计入失败)
|
|
157
157
|
- JUnit XML 状态映射:`xfailed → <skipped>`、`xpassed → <failure>`、`timeout → <error>`、`failed` 按消息类型分 `<failure>` / `<error>`
|
|
158
|
-
-
|
|
158
|
+
- 历史:耗时累计平均更新,写入前先按 `regression_threshold` 与旧均值做回归检测;内存峰值独立记录(`last_peak_memory_bytes` / `max_peak_memory_bytes` / `peak_memory_count` / `peak_memory_source`,字节),有效测量即可记录(含 failed / timeout),调度估算用历史最大值;`--update-history` 清除整条记录(耗时 + 内存)
|
|
159
159
|
- `--last-failed`:每次运行只覆写本次参与执行的用例状态,子集运行不丢失其余用例状态
|
|
160
160
|
|
|
161
161
|
### 4.2 测试双模式
|
|
@@ -166,12 +166,28 @@ raw 形态的模板和继承用例允许局部 `execution` 字典,复用完整
|
|
|
166
166
|
|
|
167
167
|
### 4.3 并行与资源调度
|
|
168
168
|
|
|
169
|
-
- LPT 策略:长任务先行;启用 history 时优先用 `.symtest` 历史 `avg_duration` 排序,其次才看声明的 `estimated_time
|
|
169
|
+
- LPT 策略:长任务先行;启用 history 时优先用 `.symtest` 历史 `avg_duration` 排序,其次才看声明的 `estimated_time`(兼容"只有内存记录、没有耗时字段"的历史条目,按 0 处理)
|
|
170
170
|
- `AtomicSemaphore` 资源池:`safe_capacity = max(1, cpu_count − 2)`;每个 case 按 `cpu_cores` acquire/release
|
|
171
171
|
- 按权重比例分配相对 CPU 核数,并自动注入 `OMP_NUM_THREADS` / `MKL_NUM_THREADS` / `NPROC`
|
|
172
172
|
- 环境变量优先级:`os.environ` < 调度器注入 < case 级 env(经 subprocess 注入,不改进程全局环境)
|
|
173
173
|
- 线程模式共享内存 + 结果/打印锁;进程模式经 process worker 隔离;可回退顺序执行
|
|
174
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
|
+
|
|
175
191
|
### 4.4 DAG 依赖调度语义
|
|
176
192
|
|
|
177
193
|
- `depends_on` 非空自动切换拓扑模式;无依赖时走零开销 fast path
|
|
@@ -185,12 +201,17 @@ raw 形态的模板和继承用例允许局部 `execution` 字典,复用完整
|
|
|
185
201
|
|
|
186
202
|
PathResolver 解析(系统命令直通、shell builtin 平台包装、复合命令拆分解析)
|
|
187
203
|
→ 声明产物清理(`execution.outputs` 声明的文件在 subprocess 启动前删除;只允许声明文件,声明目录或 workspace 根一律拒绝;路径 resolve 后必须在 workspace 内,删除失败大声失败记为执行错误;每次 attempt 都执行,`--resume` 跳过的 step 天然不清理)
|
|
188
|
-
→ subprocess 隔离执行(捕获 stdout / stderr / returncode / duration
|
|
204
|
+
→ subprocess 隔离执行(捕获 stdout / stderr / returncode / duration;Windows 测量启用时经 Job Object 以挂起创建→绑定→恢复执行整组进程,捕获进程组提交内存峰值 `PeakJobMemoryUsed`,超时经 `TerminateJobObject` 终止整组,测量失败回退普通 subprocess 路径、峰值保持未知)
|
|
189
205
|
→ 断言校验(return_code / contains / matches / compare_files)
|
|
190
206
|
→ 失败按 `retry_count` 重试
|
|
191
207
|
→ 超时 kill 整个进程组
|
|
192
208
|
→ 返回附带 `next_action_hint` 的结构化结果。
|
|
193
209
|
|
|
210
|
+
进程组内存峰值是**执行事实**(原则 2),随结果可选携带 `peak_memory_bytes` /
|
|
211
|
+
`peak_memory_source`(Windows 提交内存口径,非物理内存峰值;无可测量时字段缺席,
|
|
212
|
+
不用 0 表示未知)。聚合规则:retry 取各 attempt 最大值;sequence 取实际执行步骤的
|
|
213
|
+
最大值(步骤串行,不求和;`--resume` 跳过的步骤不补造数据)。
|
|
214
|
+
|
|
194
215
|
### 4.6 断言与文件比较集成
|
|
195
216
|
|
|
196
217
|
- `compare_files` 是一等断言,经 ComparatorFactory 按类型分发(详见 §6)
|
|
@@ -325,6 +346,12 @@ JSON/YAML 配置,学习成本更低且无交互界面维护负担。
|
|
|
325
346
|
| 项目级默认配置(`.symtest/symtest.json`) | 常用运行参数(并行、误差分析、依赖展开、报告路径)项目内固化,`symtest run` 免重复输入。三级优先级(CLI > 项目配置 > 内置默认)靠 tri-state 布尔项实现(argparse 默认 `None`,`--no-xxx` 显式关闭);未知键/坏 JSON 宽容处理只警告——配置是纯加分项,不阻断运行。替代各仓库自建入口脚本保存默认参数的用法 |
|
|
326
347
|
| `--defaults FILE` 显式默认参数文件 | 同一 workspace 需要多套默认参数(如回归 vs 验证)时免建项目 runner。显式文件**完全替代** `.symtest/symtest.json`(不叠加合并,防止验证配置漏写键时静默继承回归设置),并切换为**严格校验**(缺失/坏 JSON/未知键/类型错报错退出)——显式指定即用户意图,静默回退到另一套设置比报错更危险。默认入口保持宽容语义不变,与 `--no-config` 互斥 |
|
|
327
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 伪装),执行与判定语义完全不变 |
|
|
328
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 摘要 |
|
|
329
356
|
|
|
330
357
|
---
|
|
@@ -181,7 +181,7 @@ the exact file and field.
|
|
|
181
181
|
- JSON/YAML runners differ only by injected config_loader; common logic lives in the generic sequential / parallel runners
|
|
182
182
|
- xfail: when `expected_failure=True`, `passed → xpassed` (unexpected pass, counted as a suite failure); any non-passed status → `xfailed` (expected failure, not counted)
|
|
183
183
|
- JUnit XML status mapping: `xfailed → <skipped>`, `xpassed → <failure>`, `timeout → <error>`, `failed` split into `<failure>` / `<error>` by message type
|
|
184
|
-
- 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)
|
|
185
185
|
- `--last-failed`: each run overwrites only the statuses of executed cases; subset runs never lose states of unexecuted cases
|
|
186
186
|
|
|
187
187
|
### 4.2 Two Case Modes
|
|
@@ -193,12 +193,28 @@ JSON Schema; it is not restated here.
|
|
|
193
193
|
|
|
194
194
|
### 4.3 Parallelism and Resource Scheduling
|
|
195
195
|
|
|
196
|
-
- 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)
|
|
197
197
|
- `AtomicSemaphore` resource pool: `safe_capacity = max(1, cpu_count − 2)`; per-case acquire/release by `cpu_cores`
|
|
198
198
|
- Relative CPU cores assigned proportionally by weight; auto-injects `OMP_NUM_THREADS` / `MKL_NUM_THREADS` / `NPROC`
|
|
199
199
|
- Environment variable precedence: `os.environ` < scheduler injection < case-level env (via subprocess, never mutating global `os.environ`)
|
|
200
200
|
- Thread mode shares memory with result/print locks; process mode isolates via process workers; sequential fallback available
|
|
201
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
|
+
|
|
202
218
|
### 4.4 DAG Dependency Scheduling Semantics
|
|
203
219
|
|
|
204
220
|
- Non-empty `depends_on` automatically switches to topological mode; no deps walks a zero-overhead fast path
|
|
@@ -217,10 +233,18 @@ workspace root are always rejected; resolved
|
|
|
217
233
|
paths must stay inside the workspace, deletion failure fails loudly as an execution
|
|
218
234
|
error; runs on every attempt, and steps skipped by `--resume` are naturally not
|
|
219
235
|
cleaned) → subprocess-isolated execution (captures
|
|
220
|
-
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 /
|
|
221
237
|
matches / compare_files) → retries on failure up to `retry_count` → kills the
|
|
222
238
|
whole process group on timeout → structured result with `next_action_hint`.
|
|
223
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
|
+
|
|
224
248
|
### 4.6 Assertions and File Comparison Integration
|
|
225
249
|
|
|
226
250
|
- `compare_files` is a first-class assertion dispatched via ComparatorFactory (see §6)
|
|
@@ -232,7 +256,7 @@ whole process group on timeout → structured result with `next_action_hint`.
|
|
|
232
256
|
| State | Content | Update timing / semantics |
|
|
233
257
|
|---|---|---|
|
|
234
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 |
|
|
235
|
-
| 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 |
|
|
236
260
|
| `last_run.json` | case → last status | Overwrites executed cases; unexecuted retain old status |
|
|
237
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 |
|
|
238
262
|
| `sequence_state/cache/*.log` | Step output cache | Kept in sync; spliced back on resume |
|
|
@@ -309,8 +333,7 @@ no interactive UI maintenance burden.
|
|
|
309
333
|
| Semaphore-based CPU core management | More fine-grained than thread pool worker count; allows different cases to declare different core requirements |
|
|
310
334
|
| LPT scheduling strategy | Long tasks start first, reducing tail latency; prioritizes `.symtest` historical data |
|
|
311
335
|
| Cumulative average history update | Simple and intuitive; single anomalies are naturally diluted over many runs |
|
|
312
|
-
| Regression check before update | Compare against old average first, then update; ensures comparison is against the "historical baseline" |
|
|
313
|
-
| `.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 |
|
|
314
337
|
| Environment variable injection | Scientific computing solvers often ignore Python-level thread control |
|
|
315
338
|
| Comparator factory + plugin discovery | Creates comparators by file type; workspace `comparators/` directory for auto-discovered plugins |
|
|
316
339
|
| subprocess isolated execution | Each test case runs in an independent subprocess, ensuring tests don't affect each other |
|
|
@@ -326,6 +349,12 @@ no interactive UI maintenance burden.
|
|
|
326
349
|
| JUnit XML output | Compatible with GitLab CI / Jenkins / CircleCI and other major CI system test report formats |
|
|
327
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 |
|
|
328
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 |
|
|
329
358
|
|
|
330
359
|
---
|
|
331
360
|
|
|
@@ -1617,7 +1617,7 @@ test_cases:
|
|
|
1617
1617
|
|---|---|
|
|
1618
1618
|
| `cpu_cores` | 所需 CPU 核心数,默认 1。框架用信号量控制分配,超限任务排队等待 |
|
|
1619
1619
|
| `estimated_time` | 预估耗时(秒),用于 LPT 调度(长任务优先启动) |
|
|
1620
|
-
| `min_memory_mb` |
|
|
1620
|
+
| `min_memory_mb` | 内存需求估算量(MB)。Windows 内存管理启用时直接作为准入的需求估算;未启用时仅参与日志提示 |
|
|
1621
1621
|
| `priority` | 优先级 0-10,目前仅用于信息标注 |
|
|
1622
1622
|
|
|
1623
1623
|
框架行为:
|
|
@@ -1625,6 +1625,60 @@ test_cases:
|
|
|
1625
1625
|
- 任务启动时自动注入 `OMP_NUM_THREADS`、`MKL_NUM_THREADS`、`NPROC` 环境变量,防止求解器线程失控
|
|
1626
1626
|
- 按 `estimated_time` 降序调度(LPT 策略);若启用 `--history-dir`,优先使用历史 `avg_duration` 排序
|
|
1627
1627
|
|
|
1628
|
+
### Windows 内存感知调度(机会式准入)
|
|
1629
|
+
|
|
1630
|
+
大规模并行求解器(如 Abaqus)偶发因内存不足失败。在 **Windows + 线程模式** 下,
|
|
1631
|
+
启用 `--history-dir` 或声明 `min_memory_mb` 后,框架进入机会式内存准入:根据
|
|
1632
|
+
历史需求和当前内存压力决定是否启动新任务,减少并行引起的内存失败;允许偶发
|
|
1633
|
+
超出内存,不保证零 OOM。
|
|
1634
|
+
|
|
1635
|
+
**峰值测量**:每个命令经 Windows Job Object 以"挂起创建 → 绑定 → 恢复"方式执行,
|
|
1636
|
+
启动器及其后代进程(求解器)整组被统计**提交内存峰值**(commit memory 口径,
|
|
1637
|
+
非物理内存峰值)。retry 取各次尝试的最大值;步骤序列取实际执行步骤的最大值。
|
|
1638
|
+
启动器退出后仍等待 Job 内全部后代结束;整组进程共享命令的 `timeout`,
|
|
1639
|
+
超过期限会终止整组并报告超时,不使用固定的后代清理宽限时间。
|
|
1640
|
+
若管道读取及主进程等待已完成,但 Job 排空查询失败,则记录警告,保留命令的输出和返回码,
|
|
1641
|
+
不报告超时、不重新执行,峰值标记为未知;此时无法确认后代全部完成,关闭 Job 仍会清理残留进程。
|
|
1642
|
+
|
|
1643
|
+
**准入判据**(全部满足才启动,否则排队等待并周期重评):
|
|
1644
|
+
|
|
1645
|
+
1. CPU 令牌充足;
|
|
1646
|
+
2. 仅在峰值可能拥挤时要求峰值可能拥挤时距上次授予 ≥ 最小启动间隔(默认 1s,规则见下);
|
|
1647
|
+
3. 提交余量 ≥ 新任务估算需求 + 提交保留量(默认 2048 MB);
|
|
1648
|
+
4. 可用物理内存 ≥ 物理低水位(默认 2048 MB,独立压力检查,与任务需求无关)。
|
|
1649
|
+
|
|
1650
|
+
提交与物理两种口径分开检查、互不混用。**不做完整峰值预留**:已占用内存自然
|
|
1651
|
+
体现在系统余量中,系统余量只需覆盖新任务自身需求——避免旧策略把已分配内存
|
|
1652
|
+
重复计入而把并发压到 1。内存压力大时只暂停启动新任务,已运行任务继续执行。
|
|
1653
|
+
每次拒绝的具体原因(需求/保留量/余量/水位数值)记入调度日志,便于归因。
|
|
1654
|
+
等待准入的用例留在调度队列,后续满足准入条件且依赖已完成的用例可以先运行。
|
|
1655
|
+
|
|
1656
|
+
**需求估算优先级**:
|
|
1657
|
+
|
|
1658
|
+
1. 显式声明的 `min_memory_mb`(用户判断优先);
|
|
1659
|
+
2. history 中的历史最大峰值 × 安全系数(默认 1.2);
|
|
1660
|
+
3. 两者皆无(首次运行):使用可配置的默认需求(默认 4096 MB)——不再整池
|
|
1661
|
+
独占;首次估算不准的风险接受,运行后更新历史。
|
|
1662
|
+
|
|
1663
|
+
**准入参数配置**(`symtest.json` 的 `run` 段;CLI 第一版不提供旗标):
|
|
1664
|
+
|
|
1665
|
+
| 配置键 | 类型 | 默认值 | 说明 |
|
|
1666
|
+
|---|---|---|---|
|
|
1667
|
+
| `memory_margin` | float | 1.2 | 历史峰值估算需求的安全系数 |
|
|
1668
|
+
| `memory_commit_reserve_mb` | int | 2048 | 提交余量保留(MB),准入时需额外覆盖 |
|
|
1669
|
+
| `memory_physical_watermark_mb` | int | 2048 | 物理内存低水位(MB),低于该值暂停新任务 |
|
|
1670
|
+
| `memory_default_demand_mb` | int | 4096 | 需求未知 case 的默认估算需求(MB) |
|
|
1671
|
+
| `memory_min_start_interval_s` | float | 1.0 | 峰值可能拥挤时的最小启动间隔(秒),0 关闭 |
|
|
1672
|
+
|
|
1673
|
+
仅在存在活动任务且“活动任务估算峰值之和 + 新任务需求 + 提交保留量”大于当前提交余量时,才要求距上次授予达到启动间隔;余量充足或活动任务全部结束时立即放行。该估算可能重复计入已占用内存,只用于保守地触发间隔,不作为硬预留。快照或需求未知且存在活动任务时保守保留间隔。
|
|
1674
|
+
|
|
1675
|
+
**限制与说明**:
|
|
1676
|
+
- 内存不足持续等待(这正是防止 OOM 失败的机制),等待期间每分钟输出一次心跳日志(含拒绝原因);
|
|
1677
|
+
- 物理低水位校验:已知总物理内存时,非零水位必须严格小于总量,否则初始化抛出 `ValueError`,避免永久排队。请降低 `memory_physical_watermark_mb`,或设为 0 禁用该检查。
|
|
1678
|
+
- 估算需求加提交保留量超过系统提交上限(如 pagefile 过小,结构性不可满足)时,警告并跳过提交检查放行(物理水位与启动间隔仍生效),交由用例自身失败暴露问题;
|
|
1679
|
+
- 进程模式(`--execution-mode process`)与 Linux 暂不接入内存调度与峰值测量;
|
|
1680
|
+
- 测量失败自动回退普通执行路径,峰值标记为未知,不影响测试判定。
|
|
1681
|
+
|
|
1628
1682
|
## 历史记录与回归检测
|
|
1629
1683
|
|
|
1630
1684
|
通过 `--history-dir` 指定一个目录,框架会在该目录下维护一个 `.symtest` 文件,记录每个 case 的历史运行时间。
|
|
@@ -1632,8 +1686,9 @@ test_cases:
|
|
|
1632
1686
|
### 工作原理
|
|
1633
1687
|
|
|
1634
1688
|
1. **首次运行**:目录下没有 `.symtest`,自动创建空文件,排序仍使用配置中的 `estimated_time`
|
|
1635
|
-
2. **后续运行**:读取 `.symtest` 中的历史数据,优先使用 `avg_duration`
|
|
1689
|
+
2. **后续运行**:读取 `.symtest` 中的历史数据,优先使用 `avg_duration` 做调度排序;Windows 内存感知调度同时使用历史最大内存峰值做准入估算
|
|
1636
1690
|
3. **回归检测**:每次运行结束后,如果某 case 耗时超过历史均值的阈值倍数(默认 1.5),打印警告
|
|
1691
|
+
4. **内存峰值**:耗时只记录通过的 case,内存峰值只要有有效测量就记录(含失败/超时的 case——这些数据同样保护下一次调度决策)
|
|
1637
1692
|
|
|
1638
1693
|
### CLI 用法
|
|
1639
1694
|
|
|
@@ -1675,7 +1730,11 @@ success = runner.run_tests()
|
|
|
1675
1730
|
"case_name_1": {
|
|
1676
1731
|
"avg_duration": 3.5,
|
|
1677
1732
|
"last_duration": 3.2,
|
|
1678
|
-
"run_count": 5
|
|
1733
|
+
"run_count": 5,
|
|
1734
|
+
"last_peak_memory_bytes": 5500000000,
|
|
1735
|
+
"max_peak_memory_bytes": 6100000000,
|
|
1736
|
+
"peak_memory_count": 3,
|
|
1737
|
+
"peak_memory_source": "windows_job_commit"
|
|
1679
1738
|
}
|
|
1680
1739
|
}
|
|
1681
1740
|
}
|
|
@@ -1686,6 +1745,12 @@ success = runner.run_tests()
|
|
|
1686
1745
|
| `avg_duration` | 累计平均耗时(秒),用于调度排序和回归基线 |
|
|
1687
1746
|
| `last_duration` | 最近一次运行耗时 |
|
|
1688
1747
|
| `run_count` | 历史运行次数 |
|
|
1748
|
+
| `last_peak_memory_bytes` | 最近一次进程组内存峰值(字节,提交内存口径;Windows 内存管理启用时记录,含失败用例) |
|
|
1749
|
+
| `max_peak_memory_bytes` | 历史最大内存峰值,内存调度估算使用该值 |
|
|
1750
|
+
| `peak_memory_count` | 有效峰值测量次数 |
|
|
1751
|
+
| `peak_memory_source` | 测量来源(`windows_job_commit` = Windows Job Object 提交内存峰值) |
|
|
1752
|
+
|
|
1753
|
+
内存字段为可选:未启用测量或测量失败时不产生这些字段;旧格式 history 无需迁移即可继续使用。
|
|
1689
1754
|
|
|
1690
1755
|
### 回归警告示例
|
|
1691
1756
|
|
|
@@ -1642,7 +1642,7 @@ Only effective in thread mode. Configured via the `scheduling.resources` field;
|
|
|
1642
1642
|
|---|---|
|
|
1643
1643
|
| `cpu_cores` | Required CPU core count, default 1. The framework uses semaphores to control allocation; tasks exceeding the limit wait in queue |
|
|
1644
1644
|
| `estimated_time` | Estimated duration (seconds), used for LPT scheduling (long tasks start first) |
|
|
1645
|
-
| `min_memory_mb` |
|
|
1645
|
+
| `min_memory_mb` | Memory demand estimate (MB). Used directly as the admission demand estimate when Windows memory management is enabled; informational otherwise |
|
|
1646
1646
|
| `priority` | Priority 0-10, currently used for informational labeling only |
|
|
1647
1647
|
|
|
1648
1648
|
Framework behavior:
|
|
@@ -1650,6 +1650,84 @@ Framework behavior:
|
|
|
1650
1650
|
- Automatically injects `OMP_NUM_THREADS`, `MKL_NUM_THREADS`, `NPROC` environment variables when a task starts, preventing solver thread runaway
|
|
1651
1651
|
- Schedules by `estimated_time` in descending order (LPT strategy); if `--history-dir` is enabled, prefers historical `avg_duration` for ordering
|
|
1652
1652
|
|
|
1653
|
+
### Windows Memory-Aware Scheduling (Opportunistic Admission)
|
|
1654
|
+
|
|
1655
|
+
Large-scale parallel solvers (e.g. Abaqus) occasionally fail from memory exhaustion.
|
|
1656
|
+
On **Windows in thread mode**, once `--history-dir` is enabled or `min_memory_mb` is
|
|
1657
|
+
declared, the framework switches to opportunistic memory admission: whether to start
|
|
1658
|
+
a new task is decided from historical demand and the current memory pressure,
|
|
1659
|
+
reducing parallel memory failures; occasional overcommit is allowed and zero-OOM is
|
|
1660
|
+
not guaranteed.
|
|
1661
|
+
|
|
1662
|
+
**Peak measurement**: every command runs inside a Windows Job Object
|
|
1663
|
+
(created suspended → assigned → resumed), so the launcher and all its descendant
|
|
1664
|
+
processes (the solvers) are tracked as one group for the **commit-memory peak**
|
|
1665
|
+
(commit basis, not physical-memory peak). Retries take the maximum across attempts;
|
|
1666
|
+
step sequences take the maximum across actually-executed steps.
|
|
1667
|
+
After the launcher exits, execution waits for all descendants in the Job to finish.
|
|
1668
|
+
The whole group shares the command's `timeout`; reaching that deadline terminates
|
|
1669
|
+
the group and reports a timeout, without a fixed descendant cleanup grace period.
|
|
1670
|
+
If pipe reading and the direct-process wait have completed but the Job drain query
|
|
1671
|
+
fails, a warning is logged and the command's output and return code are preserved,
|
|
1672
|
+
without reporting a timeout or rerunning the command; the peak is marked unknown.
|
|
1673
|
+
Descendant completion cannot be confirmed in this case; closing the Job still
|
|
1674
|
+
cleans up remaining processes.
|
|
1675
|
+
|
|
1676
|
+
**Admission criteria** (all must hold to start; otherwise the task queues and is
|
|
1677
|
+
re-evaluated periodically):
|
|
1678
|
+
|
|
1679
|
+
1. CPU tokens suffice;
|
|
1680
|
+
2. only under potential peak crowding, the minimum startup interval (default 1s)
|
|
1681
|
+
has elapsed since the last grant (see below);
|
|
1682
|
+
3. commit margin ≥ the new task's estimated demand + commit reserve
|
|
1683
|
+
(default 2048 MB);
|
|
1684
|
+
4. available physical memory ≥ the physical watermark (default 2048 MB; an
|
|
1685
|
+
independent pressure check unrelated to the task's demand).
|
|
1686
|
+
|
|
1687
|
+
The commit and physical budgets are checked separately and never mixed. **No full
|
|
1688
|
+
peak reservations**: memory already in use shows up naturally in the system
|
|
1689
|
+
headroom, so the headroom check only covers the new task's own demand — avoiding
|
|
1690
|
+
the old policy's double counting that squeezed concurrency down to 1. Under memory
|
|
1691
|
+
pressure only new admissions pause; running tasks continue. Every denial records
|
|
1692
|
+
its concrete reason (demand / reserve / headroom / watermark figures) in the
|
|
1693
|
+
scheduler log for attribution.
|
|
1694
|
+
Cases waiting for admission stay in the scheduler queue. Later eligible cases
|
|
1695
|
+
whose dependencies are satisfied can run first.
|
|
1696
|
+
|
|
1697
|
+
**Demand estimate priority**:
|
|
1698
|
+
|
|
1699
|
+
1. explicitly declared `min_memory_mb` (user judgment wins);
|
|
1700
|
+
2. the historical max peak from history × safety factor (default 1.2);
|
|
1701
|
+
3. neither (first run): a configurable default demand (default 4096 MB) — no more
|
|
1702
|
+
whole-pool exclusive runs; the risk of an inaccurate first estimate is accepted
|
|
1703
|
+
and history is updated after the run.
|
|
1704
|
+
|
|
1705
|
+
**Admission parameters** (`run` section of `symtest.json`; no CLI flags in the
|
|
1706
|
+
first version):
|
|
1707
|
+
|
|
1708
|
+
| Key | Type | Default | Description |
|
|
1709
|
+
|---|---|---|---|
|
|
1710
|
+
| `memory_margin` | float | 1.2 | Safety factor applied to historical peaks for demand estimation |
|
|
1711
|
+
| `memory_commit_reserve_mb` | int | 2048 | Commit reserve (MB) the margin must additionally cover |
|
|
1712
|
+
| `memory_physical_watermark_mb` | int | 2048 | Physical memory low-water mark (MB); below it new admissions pause |
|
|
1713
|
+
| `memory_default_demand_mb` | int | 4096 | Default demand estimate (MB) for cases with no history |
|
|
1714
|
+
| `memory_min_start_interval_s` | float | 1.0 | Minimum startup interval (seconds) under potential peak crowding; 0 disables |
|
|
1715
|
+
|
|
1716
|
+
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.
|
|
1717
|
+
|
|
1718
|
+
**Limitations and notes**:
|
|
1719
|
+
- Memory shortage waits indefinitely (this is the mechanism that prevents OOM
|
|
1720
|
+
failures); a heartbeat log including the denial reason is emitted once per
|
|
1721
|
+
minute while waiting;
|
|
1722
|
+
- 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.
|
|
1723
|
+
- estimated demand plus commit reserve exceeding the system commit limit (structurally unsatisfiable, e.g. a
|
|
1724
|
+
small pagefile) warn and skip the commit check (physical watermark and startup
|
|
1725
|
+
interval still apply), leaving the problem to the case's own failure;
|
|
1726
|
+
- process mode (`--execution-mode process`) and Linux do not yet participate in
|
|
1727
|
+
memory scheduling or peak measurement;
|
|
1728
|
+
- measurement failure falls back to the plain execution path with the peak marked
|
|
1729
|
+
unknown; test verdicts are unaffected.
|
|
1730
|
+
|
|
1653
1731
|
## History & Regression Detection
|
|
1654
1732
|
|
|
1655
1733
|
Use `--history-dir` to specify a directory where the framework maintains a `.symtest` file recording each case's historical run times.
|
|
@@ -1657,8 +1735,9 @@ Use `--history-dir` to specify a directory where the framework maintains a `.sym
|
|
|
1657
1735
|
### How It Works
|
|
1658
1736
|
|
|
1659
1737
|
1. **First run**: No `.symtest` in the directory; an empty file is auto-created; ordering still uses `estimated_time` from the config
|
|
1660
|
-
2. **Subsequent runs**: Reads historical data from `.symtest`, preferring `avg_duration` for scheduling order
|
|
1738
|
+
2. **Subsequent runs**: Reads historical data from `.symtest`, preferring `avg_duration` for scheduling order; Windows memory-aware scheduling additionally uses the historical max memory peak for admission estimates
|
|
1661
1739
|
3. **Regression detection**: After each run, if any case's duration exceeds the historical average by the threshold multiplier (default 1.5), a warning is printed
|
|
1740
|
+
4. **Memory peaks**: durations are recorded only for passed cases, while memory peaks are recorded whenever a valid measurement exists (including failed/timed-out cases — that data protects the next scheduling decision just as well)
|
|
1662
1741
|
|
|
1663
1742
|
### CLI Usage
|
|
1664
1743
|
|
|
@@ -1700,7 +1779,11 @@ success = runner.run_tests()
|
|
|
1700
1779
|
"case_name_1": {
|
|
1701
1780
|
"avg_duration": 3.5,
|
|
1702
1781
|
"last_duration": 3.2,
|
|
1703
|
-
"run_count": 5
|
|
1782
|
+
"run_count": 5,
|
|
1783
|
+
"last_peak_memory_bytes": 5500000000,
|
|
1784
|
+
"max_peak_memory_bytes": 6100000000,
|
|
1785
|
+
"peak_memory_count": 3,
|
|
1786
|
+
"peak_memory_source": "windows_job_commit"
|
|
1704
1787
|
}
|
|
1705
1788
|
}
|
|
1706
1789
|
}
|
|
@@ -1711,6 +1794,12 @@ success = runner.run_tests()
|
|
|
1711
1794
|
| `avg_duration` | Cumulative average duration (seconds), used for scheduling and regression baseline |
|
|
1712
1795
|
| `last_duration` | Most recent run duration |
|
|
1713
1796
|
| `run_count` | Historical run count |
|
|
1797
|
+
| `last_peak_memory_bytes` | Most recent process-group memory peak (bytes, commit basis; recorded when Windows memory management is enabled, including failed cases) |
|
|
1798
|
+
| `max_peak_memory_bytes` | Historical max memory peak; used by memory scheduling estimates |
|
|
1799
|
+
| `peak_memory_count` | Number of valid peak measurements |
|
|
1800
|
+
| `peak_memory_source` | Measurement source (`windows_job_commit` = Windows Job Object commit-memory peak) |
|
|
1801
|
+
|
|
1802
|
+
Memory fields are optional: they are absent when measurement is disabled or fails; old-format history files load without migration.
|
|
1714
1803
|
|
|
1715
1804
|
### Regression Warning Example
|
|
1716
1805
|
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "symtest-cli"
|
|
7
|
-
version = "1.
|
|
7
|
+
version = "1.6.0"
|
|
8
8
|
description = "Regression testing for CLI applications, with multi-step workflows and numerical file comparison."
|
|
9
9
|
readme = "README.md"
|
|
10
10
|
license = { text = "MIT" }
|
|
@@ -305,6 +305,23 @@ symtest run test_cases.json --parallel --workers 4
|
|
|
305
305
|
symtest run test_cases.json --parallel --execution-mode process
|
|
306
306
|
```
|
|
307
307
|
|
|
308
|
+
On Windows in thread mode, `--history-dir` or a declared `min_memory_mb`
|
|
309
|
+
enables opportunistic memory admission: a task starts only when commit margin
|
|
310
|
+
covers its own estimated demand plus a reserve, available physical memory stays
|
|
311
|
+
above a low watermark, and, only under potential peak crowding, the minimum startup interval since the
|
|
312
|
+
last grant has elapsed. Active tasks keep no full peak reservations — memory in use shows up in
|
|
313
|
+
the system headroom — so occasional overcommit is accepted (zero-OOM not
|
|
314
|
+
guaranteed). Admission parameters are `symtest.json` `run` keys
|
|
315
|
+
(`memory_margin`, `memory_commit_reserve_mb`, `memory_physical_watermark_mb`,
|
|
316
|
+
`memory_default_demand_mb`, `memory_min_start_interval_s`). A launcher and all
|
|
317
|
+
descendants in its Job share the command's
|
|
318
|
+
`timeout`, including descendants that redirect output and outlive the launcher.
|
|
319
|
+
|
|
320
|
+
Cases waiting for admission stay in the scheduler queue, leaving workers free
|
|
321
|
+
for later eligible cases whose dependencies are satisfied.
|
|
322
|
+
|
|
323
|
+
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.
|
|
324
|
+
|
|
308
325
|
### Output
|
|
309
326
|
```bash
|
|
310
327
|
# Machine-readable JSON
|