Non-Silent Exit if Wrong Subroutine is Given - #8665
Conversation
|
Happy to merge this, but I'm curious how you encountered it? Normally, we run these tests via CTest. |
|
Thanks, @alexreinking, for the encouragement. I think Halide's apps are a gem, and I use them often. After building the linalg app, I just typed |
|
Shouldn't we print to cerr to catch this in ctest, or at least exit with status code 1? |
|
Good point about the output stream. My first inclination was to use cerr, but I did otherwise to keep symmetry with the main function. The return code would also be interesting. I didn't do it to avoid refactoring too many functions in the call stack. Happy to implement any of your suggestions, Martijn, though. |
Yeah, I think printing to |
alexreinking
left a comment
There was a problem hiding this comment.
Sorry this took so long to get in. Our buildbots have been on fire for a while
b9394e2 to
510a67a
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8665 +/- ##
==========================================
+ Coverage 69.93% 70.05% +0.11%
==========================================
Files 257 257
Lines 77537 77537
Branches 18884 18884
==========================================
+ Hits 54229 54320 +91
+ Misses 17679 17655 -24
+ Partials 5629 5562 -67 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@FabianSchuetze - to my great shame, it took me this long to realize this was approved but never merged. Fixing that now. |
The change notify users that a wrong subroutine argument is given. Currently class such as
halide_benchmarks sgemm 1024return immediately without a message.