Skip to content

feedback: config.json options that are unknown/unused in GHA summary #5

Open
@dlmiles

Description

@dlmiles

If an option is configured or mistyped, is it possible to get warning output to indicate a list of all the options seen but not understood by the flow ? This could then be summarized at the end of the GHA, but getting it in the logging is a start.

It is not clear how such feedback maybe possible due to complexities that may exist, but the hybrid nature of TT/IHP/ORFS/OpenLane makes this problem domain worse. The designer really needs feedback to identify errors early.

One solution is to record each option name successfully processed (and therefore understood) as it is used at the point of use. This might be added to the flow data state so collected as the flow progresses.

The ideal solution is for every usage of an option to have a specific step-in-flow (where) and outcome-logging (what/how) of how that option was utilized, so at the end the designer can see exactly how options interacted with which stages of the flow. But this maybe one for OpenLane and a goal with a longer term plan.

With the hybrid flow of TT just knowing the option was seen, used, considered successful is a good start, which allows for a report at the end to indicate options provided by config.json but not utilized by flow to be generated as feedback.

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