Skip to content

Logging improvements in Dynamo Paths #2399

Open
@gs-olive

Description

@gs-olive
  • Step 1 / x in logging parity between Dynamo + TorchScript
    • Ensure each high-level part of the compilation process is accurately logged to the user in a descriptive and meaningful way
    • Ensure messaging can be received and parsed effectively by users of varying levels
    • Ensure messaging is valuable to developers for debugging processes

Activity

added
component: dynamoIssues relating to the `torch.compile` or `torch._dynamo.export` paths
on Oct 16, 2023
self-assigned this
on Oct 16, 2023
peri044

peri044 commented on Oct 16, 2023

@peri044
Collaborator

Probably duplicate of #2383 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

component: dynamoIssues relating to the `torch.compile` or `torch._dynamo.export` paths

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

    Participants

    @narendasan@peri044@gs-olive

    Issue actions

      Logging improvements in Dynamo Paths · Issue #2399 · pytorch/TensorRT