ENH: Replace test hooks in simplnx production code with real failures where they are reliable
维护者通常 6 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by inventorying the hooks named in the issue and the tests that use them, including the persistence, bounded-read and selected-import areas. For each hook, determine whether a real failure reliably reaches the same step on Linux, Windows and macOS CI. Replace and remove hooks only when that path is reliable and simplifies both test and production code; keep hooks for the listed failure cases that real failures cannot reliably reach.
由索引模型根据 Issue 内容生成。
描述
Summary
Replace test hooks in simplnx production code with real failures where a real failure reliably reaches the same step, and remove the hooks that this replaces. This is a follow-up to the out-of-core review PR tree, mainly #1933 (checked flush), #1934 (selected import) and #1935 (bounded reads). Those PRs keep their hooks, and the review decided to do this work here, hook by hook.
How it works now
Many failure tests use fault injection that is compiled into the production libraries when SIMPLNX_BUILD_TESTS is ON. Examples:
ParallelChunkCodec.hpp:SetCodecIoObserverForTesting,InjectCodecFaultForTesting, theLegacyPayload...ForTestingscopes and theSIMPLNX_OBSERVE_*macros that wrap HDF5 calls.ImportH5ObjectPathsAction.hpp:setPublicationFaultForTestingand related functions. Most of these go away with the smaller selected-import design (separate issue).GroupIO.hpp:FailNextGroupConstructionForTesting.WindingTransferWarnings.hpp:SetWindingWarningFailureForTestingandMaybeFailWindingWarningForTesting.IdentifySampleCCL.hpp: the slice observer, extra allocation and diagnostic controls.BoundedRead.hpp:MakeSuccessWarningsForTesting.
The hooks add code, state and exported functions to shipping headers, and tests that depend on them break when the code is simplified. Once DREAM3D-NX BlueQuartzSoftware/DREAM3DNX#1247 merges, release presets build with SIMPLNX_BUILD_TESTS OFF, so the hooks will not be in shipped libraries.
Requested change
For each hook:
- Replace it with a real failure (a read-only or missing file, a removed group, a corrupted compressed chunk, a directory that cannot be created) when that failure reliably reaches the intended step on Linux, Windows and macOS CI, and when the change makes the test and the production code simpler. Then remove the hook.
- Keep it when no real failure reliably reaches the step. Examples: a failure after publication or during rollback, a second-chunk read failure, a failure during cleanup or checked close, two failures at once, and allocation failures.
- Do not weaken the failure assertions, and do not add a new abstraction only to remove hooks.
Which hooks can be replaced is still open. The first step is an inventory of each hook, the tests that use it, and whether a real failure reaches the same step.
The design reviews list this as persistence D7, bounded-reads D4 and selected-import D7. The SimplnxOoc hooks are a separate issue in that repository.
- 主要语言
- C++
- 星标
- 18
- 派生
- 15
- 平均合并
- 4 天 23 小时
- 30 天内合并 PR
- 42
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
BlueQuartzSoftware/simplnx 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
BlueQuartzSoftware/simplnx#1987 ·
维护者通常 6 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 74/100
BlueQuartzSoftware/simplnx#1980 ·
维护者通常 6 天内回复
-
Testing
难度 2/5 1-3 小时 新手友好度 62/100
BlueQuartzSoftware/simplnx#1979 ·
维护者通常 6 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 65/100
BlueQuartzSoftware/simplnx#1978 ·
维护者通常 6 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
BlueQuartzSoftware/simplnx#1945 ·
维护者通常 6 天内回复
查看 BlueQuartzSoftware/simplnx 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
HarperFast/rocksdb-js#1118 ·
维护者通常 1 天内回复
-
bug triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
26.04 bug dark-mode Easy Hack impress symptom: visual
难度 2/5 1-3 小时 新手友好度 68/100
CollaboraOnline/online#16421 · 1 条评论 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 63/100
telegramdesktop/tdesktop#31653 ·
维护者通常 1 天内回复
-
area/cs bug
难度 2/5 1-3 小时 新手友好度 82/100
ydb-platform/ydb#59881 · 1 条评论 ·
维护者通常 1 天内回复