test: add 3d euler beam red fortran tests

2026-06-11 14:06:36 +09:00
parent a07a92ed4b
commit a3b5d7d383
11 changed files with 830 additions and 10 deletions
@@ -0,0 +1,67 @@
+# 3D Euler-Bernoulli Beam UEL RED Test Report
+
+## Metadata
+- feature_id: uel-3d-euler-beam
+- source_reference_models: `docs/reference-models/uel-3d-euler-beam.md`
+- status: red-evidence-recorded
+- owner_agent: implementation-agent
+- date: 2026-06-11
+
+## Scope
+
+This report records the step 6 RED evidence after adding no-Abaqus Fortran tests and `tests/fortran/manifest.json`.
+
+Production Fortran source was not added in this step. The expected RED condition is a compile failure from missing planned production source:
+
+- `src/fortran/uel_3d_euler_beam_kernel.f90`
+- `src/fortran/uel_3d_euler_beam_abi_adapter.f90`
+
+## Test Files Added Before Production Code
+
+| manifest_test | source file |
+| --- | --- |
+| `uel_3d_euler_beam_kernel_stiffness` | `tests/fortran/uel_3d_euler_beam/test_kernel_stiffness.f90` |
+| `uel_3d_euler_beam_kernel_transform_modes` | `tests/fortran/uel_3d_euler_beam/test_kernel_transform_modes.f90` |
+| `uel_3d_euler_beam_abi_static` | `tests/fortran/uel_3d_euler_beam/test_abi_static.f90` |
+| `uel_3d_euler_beam_invalid_inputs` | `tests/fortran/uel_3d_euler_beam/test_invalid_inputs.f90` |
+| shared support | `tests/fortran/uel_3d_euler_beam/test_support.f90` |
+
+## Command Log Summary
+
+| order | command | exit_code | result | evidence |
+| --- | --- | --- | --- | --- |
+| 1 | `python -m json.tool tests/fortran/manifest.json` | 0 | pass | manifest JSON parsed successfully |
+| 2 | `python -m unittest discover -s scripts -p "test_*.py"` | 0 | pass | 56 Python harness tests passed |
+| 3 | `python scripts/validate_reference_artifacts.py` | 0 | pass | reference artifact metadata validation succeeded |
+| 4 | `python scripts/validate_fortran.py` | 1 | environment failure before RED | current `cmd.exe` child process sees empty `%PATH%`; nested `cmd` command is not found |
+| 5 | `$env:PATH='C:\Windows\System32;C:\Windows;C:\Users\user\miniforge3'; C:\Users\user\miniforge3\python.exe scripts/validate_fortran.py` | 1 | expected RED | `ifx` reached compile and failed because `src/fortran/uel_3d_euler_beam_kernel.f90` does not exist |
+| 6 | `python scripts/validate_workspace.py` | 1 | environment failure before RED | reference validation passed, then Fortran validation hit the same nested `cmd` lookup issue |
+| 7 | `$env:PATH='C:\Windows\System32;C:\Windows;C:\Users\user\miniforge3'; C:\Users\user\miniforge3\python.exe scripts/validate_workspace.py` | 1 | expected RED | reference validation passed, then Fortran validation failed on missing production kernel source |
+| 8 | `$env:HARNESS_FORTRAN_VALIDATION='detect'; python scripts/validate_workspace.py` | 0 | pass | reference validation passed; Fortran manifest/compiler detection mode produced no compile commands |
+
+## RED Failure Classification
+
+- classification: `fortran-compile`
+- first implementation-owned failure after environment normalization: missing planned production source
+- primary evidence tail:
+
+```text
+xfortcom: Severe: No such file or directory
+... file is 'C:\git\AbaqusSubroutineDev\src\fortran\uel_3d_euler_beam_kernel.f90'
+compilation aborted for C:\git\AbaqusSubroutineDev\src\fortran\uel_3d_euler_beam_kernel.f90 (code 1)
+```
+
+The subsequent module import errors in `test_kernel_stiffness.f90` are secondary to the missing kernel module source.
+
+## Environment Note
+
+This Codex process can find `cmd.exe` from PowerShell and Python, but a child `cmd.exe` invoked during `validate_fortran.py` sees an empty `%PATH%` unless a minimal `PATH` is set explicitly. The normalized command above confirms that Intel oneAPI `ifx` is available through the configured oneAPI env script and that the actionable RED failure is the missing production source, not a missing compiler.
+
+## Handoff to Step 7
+
+Implement the minimum production Fortran needed to turn the four manifest tests GREEN:
+
+- `src/fortran/uel_3d_euler_beam_kernel.f90`
+- `src/fortran/uel_3d_euler_beam_abi_adapter.f90`
+
+The Abaqus fixed-form `UEL` wrapper remains planned for the implementation gate but is not required to satisfy these no-Abaqus RED tests unless the step 7 plan explicitly includes it.