You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the tests currently don't do anything. I added a panic inside the #[cfg(feature = "bios")] block inside run_test_kernel_internal and it still passes even with the bios feature explicitly enabled. I think this is because features do not get passed on to the test runner crate.
I fixed this by adding a feature dependency, but I'm not entirely sure if that is the proper way to do it. The tests take considerably longer now, so I think that's good.
Thanks a lot for reporting! Looks I made the mistake to disable the features in #351. I needed to remove the features because of a bug in cargo that led to errors at publish time: rust-lang/cargo#12225 . However, I should have enabled these features unconditionally instead of disabling them. I'll prepare a fix!
The test runner was accidentally disabled in #351, in an attempt to fix the publish errors introduced by #304 (caused by a bug in cargo: rust-lang/cargo#12225). As a result, the test runner became a no-op as neither the bios nor the uefi features were enabled.
This commit fixes the issue by enabling both features by default. Once the cargo bug is fixed, we might want to switch back to the feature configuration added of #304.
Fixes#405
It looks like the tests currently don't do anything. I added a panic inside the
#[cfg(feature = "bios")]
block insiderun_test_kernel_internal
and it still passes even with the bios feature explicitly enabled. I think this is because features do not get passed on to the test runner crate.I fixed this by adding a feature dependency, but I'm not entirely sure if that is the proper way to do it. The tests take considerably longer now, so I think that's good.
The text was updated successfully, but these errors were encountered: