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
fix bug by building the minimal version of libhermit #160
Conversation
@jschwe It seems to work... |
@stlankes Have you tried building and running an application?
|
It works only on uhyve, QEMU depends on PCI.... That is the reason, why I don't test it within GitHub Actions. In the future, I want to support of Qemu's Micro VM (https://github.com/bonzini/qemu/blob/master/docs/microvm.rst). Currently, it doesn't run on it. I have to check, why it isn't working on this setup. |
Ah okay, that explains it. |
You are right, I fixed it |
.github/workflows/nightly.yml
Outdated
@@ -88,6 +88,9 @@ jobs: | |||
echo "C:\Program Files\qemu" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append | |||
echo "C:\Program Files\nasm" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append | |||
if: ${{ matrix.os == 'windows-latest' }} | |||
- name: Building minimal kernel | |||
run: | |||
cargo build -Z build-std=std,core,alloc,panic_abort --target x86_64-unknown-hermit --manifest-path=Cargo.toml --no-default-features |
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.
I think you need to specify the crate you want to build with --no-default-features
, e.g. by adding -p rusty_demo
.
bors r+ |
160: fix bug by building the minimal version of libhermit r=stlankes a=stlankes This PR should solve issue #157 In addition, I add a small test to build the minimal configuration. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: Stefan Lankes <stlankes@users.noreply.github.com>
Build failed: |
bors retry |
160: fix bug by building the minimal version of libhermit r=stlankes a=stlankes This PR should solve issue #157 In addition, I add a small test to build the minimal configuration. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: Stefan Lankes <stlankes@users.noreply.github.com>
Build failed: |
It appears that both the integration tests and the multithreaded uhyve test is failing. The multithreaded uhyve tests crashes, but still seems to exit with 0, which causes the test to appear as passed, even though it should have failed. I'll open an issue over at uhyve to track this (Edit: We already have issue 7 tracking this) I also noticed, that the way I'm dumping the stdout in the integration tests does not really result in very readable output, so I'll open a PR to improve that in the next days. |
The current version of integration tests crahs sometime. This is failure in uhyve and temporary disable these tests.
bors r+ |
160: fix bug by building the minimal version of libhermit r=stlankes a=stlankes This PR should solve issue #157 In addition, I add a small test to build the minimal configuration. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: Stefan Lankes <stlankes@users.noreply.github.com>
A valid exit code means that a thread calls the system call `exit`. In this case, we have to terminate all threads like the behaviour of `exit`. This current version is the reason that PR `hermit-os/kernel#160` doesn't pass all tests.
Build failed: |
68: revise exit handling r=stlankes a=stlankes A valid exit code means that a thread calls the system call `exit`. In this case, we have to terminate all threads like the behaviour of `exit`. This current version is the reason that PR `hermit-os/kernel#160` doesn't pass all tests. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de>
A valid exit code means that a thread calls the system call `exit`. In this case, we have to terminate all threads like the behaviour of `exit`. This current version is the reason that PR `hermit-os/kernel#160` doesn't pass all tests.
68: revise exit handling r=stlankes a=stlankes A valid exit code means that a thread calls the system call `exit`. In this case, we have to terminate all threads like the behaviour of `exit`. This current version is the reason that PR `hermit-os/kernel#160` doesn't pass all tests. Co-authored-by: Jens Breitbart <jbreitbart@gmail.com> Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
bors r+ |
160: fix bug by building the minimal version of libhermit r=stlankes a=stlankes This PR should solve issue #157 In addition, I add a small test to build the minimal configuration. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: Stefan Lankes <stlankes@users.noreply.github.com>
Build failed: |
bors r+ |
160: fix bug by building the minimal version of libhermit r=stlankes a=stlankes This PR should solve issue hermit-os#157 In addition, I add a small test to build the minimal configuration. Co-authored-by: Stefan Lankes <slankes@eonerc.rwth-aachen.de> Co-authored-by: Stefan Lankes <stlankes@users.noreply.github.com>
This PR should solve issue #157 In addition, I add a small test to build the minimal configuration.