-
Notifications
You must be signed in to change notification settings - Fork 23
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
Removing black-parrot-tools and black-parrot-sdk #2660
base: main
Are you sure you want to change the base?
Conversation
Drive-by comment: Maybe in the future the tests should be somewhat separate from submodules; have a file with a list of git URLs and commit-hashes that are fetched when tests are run, but not by default as submodule (as submodule sortof imply that it is a necessary build-resource). |
I think the reason is the bot that tries to autoupdate those submodules... |
but could it also just auto-update a file with |
I was not the one that set it up, it was also just a drive-by comment ;) Maybe @kgugala knows if Note that the CI does |
(note that this MR cannot be merged as-is because it makes black parrot tests red) |
Oh, I see there’s a useless Makefile dependency in BP to the tools and sdk. I’ll push a fix and then bump BP to fix it |
Okay, I think that bump should make tests green |
I believe you would also need to remove the BP tests (as those failed here). Why do you need to drop the submodule? All the optional submodules (the ones we use for testing, but not required to build the tool) are marked with |
why would we be removing BP tests? |
I think the tests failed as result of the bump, looks the patch is no longer valid. Will investigate |
Hm not sure why the ASIC synthesis fails if the other two are working. Any insights? |
These don't actually do anything for the synlig built, but take a lot of space and time to clone