Skip to content

Unique naming for torchrun directories #59

@michaelmckinsey1

Description

@michaelmckinsey1

I am encountering an issue when submitting multiple jobs using torchrun-hpc. If these are granted an allocation at the same time the directory naming structure will conflict, if ran from the same directory at the same second. I don't think this is too uncommon to expect, for users submitting 10+ jobs at the same time. Example of directory naming: torchrun_hpc-scaffold_2026-01-28_06h25m09s

I think the most trivial change would be to add ms to the end, which is significantly less likely to conflict. Even better would be a solution that is fully unique, like scheduler jobids, but this would not apply if running interactively.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions