Repository navigation
Tracking issue for test runner. It is and has been failing #28
Description
Activity
Yes, I mentioned this somewhere the other day. You can run tests if you run them individually, but you cannot run all the tests with "cargo test". I would love to fix this, especially because of how many tests I could add. I think that it would be a great step forward to have the ability to test all the modules and functions of the kernel. How do you think we should go about doing this?
I had tried to find out how to assign this to me but didn't see the option. I'm still learning the build environment so no clear path forward. I'm trying to start with the basics to get a simple build but have been running into errors when I try to do a "cargo boot image". the errors are all related to missing things like Ok() and Err(). it is apparent that something is missing in my simple test environment. is there a chat channel related to this os?
hi, i am interested to build our app on your operating system, is there a possible way that we can work together? im veronica and you can reach me out in telegram veronicaandrino , i tried to find you in twitter but i cant find it, so @davethiede @Kepler-Br @danielteberian so is it possible to meet on call to discuss what we are building? thanks.
I don't have Discord (I don't use it), but we can contact each other via Github, email, or something like that.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The tests should complete successfully and cargo test exit gracefully.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional information
qemu-system-x86_64 --version]rustc --version] rustc 1.73.0-nightly (0e8e857b1 2023-07-16)Additional context
Add any other context about the problem here.