-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
properly flush batch #5565
base: main
Are you sure you want to change the base?
properly flush batch #5565
Conversation
Signed-off-by: Jess Frazelle <[email protected]>
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5565 +/- ##
==========================================
- Coverage 86.43% 86.38% -0.06%
==========================================
Files 97 97
Lines 37224 37244 +20
==========================================
- Hits 32176 32174 -2
- Misses 5048 5070 +22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
// Flush the batch with all the end commands. | ||
// If we don't do this then some programs might not fully finish executing. | ||
self.engine | ||
.flush_batch(true, SourceRange::default()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty sure this needs to be inside execute_and_build_graph()
so that any commands are captured in the artifact graph.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh shit fair
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh hey thats. how i can test it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will do tomorrow my brain is fried today
we saw in kcl.py that programs were not finsihing executing when in kcl.py
i can test this in this PR #5553 but like waiting on an engine side thing so either you can wait to merge or whatever i did a temp fix in kcl.py in the interim
i cant test this w a snapshot since we will zoom to fit on it flushing the batch anyways