Tracking issue for test runner. It is and has been failing

[davethiede]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. cargo test

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

• Architecture: [e.g. x86_64, ARMv7] x86_64
• OS: [e.g. Windows 10, Ubuntu 21.10] archlinux current
• Build environment: [e.g. WSL2/Docker/plain linux] plain linux
• QEMU version: [paste output from qemu-system-x86_64 --version]
• rustc version: [paste output from rustc --version] rustc 1.73.0-nightly (0e8e857b1 2023-07-16)
• Commit hash: [link to commit from which binary was built. Do not paste link to main or any other branch head. Use concrete commit hash] This has been an ongoing issue tag:v0.17.4+6

Additional context Add any other context about the problem here.

[danielteberian]

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?

[davethiede]

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?