Since this will make simulation and hardware tests fail, could you make corresponding PR in sel4test (which we won't merge) that removes the const qualifier from the test schedule there?

With that, we can use Test with to make sure that the microkit branch keeps passing sel4test.

I wonder if const volatile is what to use them. These are still runtime constants, right?

I wonder if const volatile is what to use them. These are still runtime constants, right?

They are still runtime constants, yes

Since this will make simulation and hardware tests fail, could you make corresponding PR in sel4test (which we won't merge) that removes the const qualifier from the test schedule there?

With that, we can use Test with to make sure that the microkit branch keeps passing sel4test.

I've done this (see seL4/sel4test#126). How would I go about changing which seL4test branch this PR is tested with?