-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
backport to fix #16132 #16372
base: Pharo11
Are you sure you want to change the base?
backport to fix #16132 #16372
Conversation
Thanks for opening this pull request! Now continious integration (CI) will build Pharo with your change and run all tests. This might fail due to many reasons! Please check if your PR breaks the build or makes tests fail. Feel free to add comments to the PR. After this, before your PR can be merged it needs one or more reviews. Do not hesitate to ask people (on the Mailinglist or Discord) to help! When the CI shows no problems and there are positive reviews, your PR will be merged. |
I restarted the CI |
It has been two times that the build fail with:
|
Do we keep backporting to P11 when P12 is stable? |
Nope but this is one is important so if it takes less than 5 min let us do it |
The problem is that the P11 build seems to fail and I don't know why :/ |
Backport to have this fix: https://github.com/pharo-project/pharo/pull/16206/files on Pharo11