-
Notifications
You must be signed in to change notification settings - Fork 45
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
Dev branch requested for changes | Master becomes unstable sometimes? #61
Comments
Dear Vijay, It's great to hear that you succeeded in building and running CheriBSD with cheribuild. I apologize for the instability over the past few weeks/months. We have been trying to add support for RISC-V and been testing MIPS less in the process. This has resulted in various unnecessary build failures. By instability, do you mean instability of cheribuild itself? Or the projects being built with cheribuild? For the dependent projects, I have been trying to improve our continuous integration to allow better pre-merge checks on pull requests. This should result in fewer build failures. The current phase of large breaking changes should be over now and all branches will be more stable. Nevertheless, there are many configuration options that can be set and we can't test all combinations but the default cheribuild settings should be supported. We will continue to work on improving stability. The current state is as follows:
|
We are using dev branches for cheribsd/llvm/qemu, so this should be fixed now. |
Dear Cheribuild Team,
Hope you are doing well. Thank you for your support.
Recently, we have been trying to compile Cheri using Cheribuild. Few times, it was successful and we were able to compile and ssh to the cheribsd. However, few times, because of the recent changes, we got compilation errors. Would it be possible for you to create a dev branch or any other branch for changes? and once it is stable, we can merge to master.
This would make master branch more stable and compilation error-free.
Thank you
Yours Sincerely,
Vijay
The text was updated successfully, but these errors were encountered: