-
Notifications
You must be signed in to change notification settings - Fork 29
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
Integration tests: Use default profile #195
Conversation
Codecov Report
@@ Coverage Diff @@
## master #195 +/- ##
=======================================
Coverage 20.49% 20.49%
=======================================
Files 17 17
Lines 2654 2654
=======================================
Hits 544 544
Misses 2110 2110 Continue to review full report at Codecov.
|
bors r+ |
195: Integration tests: Use default profile r=stlankes a=mkroening For easy integration tests of gdbstub, I need the `dev ` `opt-level` to be 0. On `release`, `opt-level` is 3 by default. 197: CI: Download Git-LFS files r=stlankes a=mkroening This is required for the [`test_vm.*`](https://github.com/hermitcore/uhyve/blob/3b70087e3612e55ddce7888ce1b9fe91ca8596c9/src/vm.rs#L856-L907) to work correctly. Without this, they are not operating on the real files, but mere placeholders. We need `git-lfs` to be installed on our runner for this. Found via #192. 200: CI: Capture test output r=stlankes a=mkroening This avoids GitHub check annotations about expected panics. This reverts 4e222b7. Co-authored-by: Martin Kröning <mkroening@posteo.net>
bors r- |
Canceled. |
bors try |
@mkroening have you investigated, why this test fails? |
The failure should be spurious. bors try While |
Well, this only affects the integration tests, so we can merge it now. I'm just curious why it failed before. But nevertheless: bors r+ |
As I said, the failure was spurious and had nothing to do with this PR. Bors commands have to be at a newline: |
For easy integration tests of gdbstub, I need the
dev
opt-level
to be 0.On
release
,opt-level
is 3 by default.