derive_metric results are wrong, or aggregation fails, for runs that failed under ignore_failures=True
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read extract_df_from_data in nsight/extraction.py to follow how failed runs produce derived metric rows, then review the aggregation in nsight/transformation.py. Run the focused tests in tests/test_collection.py and compare failed-run rows with successful derived metrics. Done means failed runs retain the successful metrics’ names and units without a false warning, including the documented all-runs-failed behavior.
由索引模型根据 Issue 内容生成。
描述
Description
When a run fails inside nsight.annotate(..., ignore_failures=True), derive_metric is not called for it (there are no values). The derived row of that run is then recorded as if derive_metric had returned a bare number: the metric is named after the function, the unit is NaN, and a "does not have a unit specified" warning is emitted.
Case A, derive_metric returns a dict and one configuration always fails:
import nsight
import torch
def per_element(time_ns, n):
return {
"elements_per_ns": (n * n / time_ns, "elem/ns"),
"ns_per_element": (time_ns / (n * n), "ns/elem"),
}
@nsight.analyze.kernel(configs=[(64,), (128,)], runs=2, derive_metric=per_element)
def bench(n):
a = torch.randn(n, n, device="cuda")
with nsight.annotate("add", ignore_failures=True):
if n == 128:
raise RuntimeError("this config is not supported")
_ = a + a
print(bench().to_dataframe()[["Annotation", "n", "Metric", "NumRuns", "Unit"]])
UserWarning: Derived metric 'per_element' does not have a unit specified. Return a tuple (value, unit) instead of just the value. ...
Annotation n Metric NumRuns Unit
add 64 gpu__time_duration.sum 2 ns
add 128 gpu__time_duration.sum 0 ns
add 64 elements_per_ns 2 elem/ns
add 64 ns_per_element 2 ns/elem
add 128 per_element 0 NaN
n=128 has a row for a metric called per_element, and no rows for elements_per_ns / ns_per_element.
Case B, derive_metric returns (value, unit) and only one of several runs of a configuration fails (runs=3, the second run raises):
AssertionError: Column 'Unit' has multiple values in group: <StringArray>
['elem/ns', nan]
The call fails in aggregate_data and returns nothing, although two runs succeeded.
Expected
The failed run counts as a missing value of the same derived metrics, with their units, the way gpu__time_duration.sum is already reported for the failed configuration above. No unit warning when derive_metric returns units. The ignore_failures docstring says "The measured metric for this run will be set to NaN".
Where
extract_df_from_data in nsight/extraction.py: derived_metric is None for a failed run and falls into the branch for a scalar return value. In case B the Unit column then has two values in one group, which the aggregation in nsight/transformation.py rejects.
Environment
nsight-python main at c89d4b5, Python 3.12.3, pandas 3.1.1, Linux x86_64.
How this was checked: no GPU was available, so the outputs above come from the same decorator and annotation calls with the profiling backend replaced by a mock. The mock reports the kernel as fake_kernel, and that column is cut from the table above. The decorator, run loop, extraction and aggregation were the real nsight code. The claim that the real NCU and CUPTI collectors pass no values for a failed run is based on reading extraction.py and collection/cupti.py, not on a GPU run.
Draft PR #74 changes the same function but not this part. A fix is ready if you approve it: it gives failed-run rows the metric names and units of a successful run, and adds two unit tests in tests/test_collection.py. One open point is what to report when every run of a configuration fails, because then there is no successful run to copy names and units from. The fix keeps today's output for that case, without the false warning.
This was found with an AI coding assistant (Claude Code, claude-fable-5-2), which also wrote and ran the mocked repro and drafted this report.
- 主要语言
- Python
- 星标
- 301
- 派生
- 23
- 平均合并
- 2 天 20 小时
- 30 天内合并 PR
- 12
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
NVIDIA/nsight-python 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
NVIDIA/nsight-python#88 ·
维护者通常 1 天内回复
-
Enable collecting metrics from a set可能重新可做 @Alok-Joshi 于 57 天前认领,目前没有进行中的 PR。 未关闭
NVIDIA/nsight-python#7 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 NVIDIA/nsight-python 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
FAIRmat-NFDI/pynxtools#861 ·
-
Criteria can pass when the deliverable is missing可能已有人在做 @clementtisseau 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
harveyai/harvey-labs#217 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
priority/medium roadmap/v1.1.1 stakeholder/rapr type/bug
难度 2/5 1-3 小时 新手友好度 83/100
databrickslabs/ontos#1420 ·
维护者通常 3 天内回复
-
[Bug] method_logger uses fragile definition-time inspect stack frame instead of func.__qualname__未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复