Skip to content

Explain how to interpret recompile_reasons.json #153

@xmfan

Description

@xmfan

Internal ref: https://fb.workplace.com/groups/1075192433118967/posts/1799968213974715/?comment_id=1800002880637915&reply_comment_id=180041419393011

From @anijain2305:

For 1, the recompile reasons are known to be  hard to read.

This is the way to interpret the compiled reasons.
"For these set of inputs, all the previously compiled entries failed. For each  previously compiled entry, here is the reason"

In your case you are looking at 0/6th frame and therefore you have 6 previous entries. And suppose 0/6th frame has state equals not None.

This is saying that at the time of 5,4, 2 compile entries, the state was None.

This does not mean that there 5,4 and 2 represent 3 different values of state.

Hopefully, this also explains why recompile reasons vary from frame to frame (they are telling for each new frame, why the previously compiled frames were inadequate).

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