Closed tarun292 closed 1 week ago
Note: Links to docs will display an error until the docs builds have been completed.
As of commit 5a4a5bd09b65088d630580ddba9030bb834db166 with merge base 47a29a13f4f2574b6787be03249633d5531b795a (): :green_heart: Looks good so far! There are no failures yet. :green_heart:
This comment was automatically generated by Dr. CI and updates every 15 minutes.
This pull request was exported from Phabricator. Differential Revision: D57517927
This pull request was exported from Phabricator. Differential Revision: D57517927
This pull request was exported from Phabricator. Differential Revision: D57517927
This pull request was exported from Phabricator. Differential Revision: D57517927
This pull request was exported from Phabricator. Differential Revision: D57517927
This pull request has been merged in pytorch/executorch@07dcf35b3e71c940e12385cc6cbd7e32b29c8e21.
Summary: Currently when we call
get_etdump_data()
we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer.In order to support this, adding a
ETDumpGen_Done
state to which we move after callingget_etdump_data()
. When this state is detected increate_event_block
we implicitly callreset()
and thus enabling writing to the flatbuffer again without any user intervention.Differential Revision: D57517927