Skip to content

Embed run_uuid in POST script args; bump to 0.1.0rc11#3

Merged
iross merged 1 commit into
mainfrom
fix/post-run-id-hint-v2
Jun 5, 2026
Merged

Embed run_uuid in POST script args; bump to 0.1.0rc11#3
iross merged 1 commit into
mainfrom
fix/post-run-id-hint-v2

Conversation

@iross

@iross iross commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • job_ad_file is silently ignored by the HTCondor schedd, so .ad files are never written and nearly all POST-script provenance events land in unknown.ndjson
  • daggen.py now embeds --run-id <run_uuid> directly in SCRIPT POST args at DAG generation time
  • post.py accepts --run-id as a final fallback after the ClassAd and .run_id marker lookups both fail
  • .ad files are still read when present (for wall_time, GPU usage, etc.); only the run_id dependency is removed

Test plan

  • 3 new tests covering run_id_hint fallback, ClassAd precedence over hint, and --run-id CLI flag
  • Full suite: 170 passed

🤖 Generated with Claude Code

job_ad_file is silently ignored by the HTCondor schedd (likely unsupported
in the version running on the submit machine), so .ad files are never written
and nearly all POST-script provenance events land in unknown.ndjson.

Fix: daggen.py embeds --run-id <run_uuid> directly in the SCRIPT POST args at
DAG generation time. post.py accepts --run-id as a final fallback after the
ClassAd and .run_id marker lookups both fail. The .ad file is still read when
present (for wall_time, GPU usage, etc.); only the run_id dependency is removed.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
@iross iross merged commit 5253746 into main Jun 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant