-
Notifications
You must be signed in to change notification settings - Fork 31
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
sel4bench build is failing for Quartz64 #32
Comments
As a meta observation: it looks like we need a better see all minimally necessary checks passing when we accept a platform port. Currently, we need the platform to exist in the platform list for a build check to appear on GitHub, but once that platform is in the list, CI will fail until all necessary patches are merged and will block other builds. Something that could potentially help is a way of switching on a disabled platform for a specific pull request only. |
For this specific case: the platform doesn't have a timer yet, so it doesn't really make sense to build sel4bench for it. There is probably a mechanism for that already somewhere that is just not used here. |
It is still failing with another issue:
This could be a fix: seL4/seL4_libs#71 |
Seem this patch gets us a bit further in the build., see https://github.com/seL4/sel4bench/actions/runs/3602291771/jobs/6069082715
|
The generic timer ltimer driver can be used if the KernelArmExportPCNTUser AND KernelArmExportPTMRUser kernel features are enabled. These features are only for development, but could work for sel4bench. |
This is temporary until seL4/sel4bench#32 is fixed. Signed-off-by: Gerwin Klein <[email protected]>
I'm temporarily switching off QUARTZ64 until this issues is resolved, so that we can get sel4bench results in the meantime. |
This is temporary until seL4/sel4bench#32 is fixed. Signed-off-by: Gerwin Klein <[email protected]>
I thought I had seen this building successfully before, but it seems that was not the case.
Error message is:
Also here: https://github.com/seL4/sel4bench/actions/runs/3527176346/jobs/5915946235
The text was updated successfully, but these errors were encountered: