Repository navigation
annotate(hypercall/lseek): make sure missing constants cause compile-time error - #1170
Conversation
mkroening
left a comment
There was a problem hiding this comment.
Will this not error in CI anyway? Or is this about local development somehow? 🤔
|
It currently only produces a warning. Feel free to try. |
|
It produces a warning locally, sure. That decision was intentional to not hinder local development by erroring on every warning. But in CI it should already be an error: uhyve/.github/workflows/ci.yml Line 123 in f9de15f |
|
The problem is that this tiny piece of code completely breaks on missing constants and relying on CI for that feels like a bad idea, as it runs a bit too late (i.e. causes unnecessary CI runs, which waste time and resources). |
|
Okay so, yes, this is about local development. That answers my question. :D |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1170 +/- ##
==========================================
- Coverage 76.61% 76.28% -0.34%
==========================================
Files 28 28
Lines 3605 3605
==========================================
- Hits 2762 2750 -12
- Misses 843 855 +12 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
CI failure is unrelated (timeout). |
|
Thx! |
Related: #1145 (comment)
In the Uhyve V2 Interface PR, the problem popped up that missing re-exports of
SEEK_*constants only show up as warnings, and this gets fixed by this PR.