-
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
Handle introduction of ref_typespec in UHDM/Surelog #2000
Conversation
@wsipak @kbieganski the next time you want to update Surelog, this PR needs to be merged. |
looks like this code doesn't build, @hs-apotell can you take a look at this? |
@kgugala CI isn't pulling the latest from UHDM and Surelog. This PR requires at least 893badb9ab9f382547b77cffaaa159f146f4f64c from UHDM and 7cb11f24f13a6fa4fc0f583d599736b6aeeddf86 from Surelog. CI is reporting UHDM checked out 21699af32d84445ab997373e641bb734fbf34f33 and Surelog checked out at f1dfa053a04256aea769baa93d4d2e7cea5c1807 both of which aren't at head. |
@hs-apotell CI is not affecting which commit it takes, its the repo -- CI is just pulling the submodules in third-party: https://github.com/chipsalliance/synlig/tree/main/third_party so if you want to use a different commit you have to update your fork and push force. |
efe70d9
to
d7e2c0a
Compare
@pgielda Done! I wrongly assumed that CI was forcing a pull from Surelog master (like it does on Surelog CI). I have updated third_party/Surelog. Can you approve a PR verification build? |
there seem to be some segfaults, there is some hint from ASAN in the EnumBases test:
|
@hs-apotell no, we pin e.g. surelog and yosys versions (as well as other versions) and have a dependabot that tries to bump them to main. Its merged if green, but often its not (due to changes that need an implementation in the plugin or simply bugs/regressions on upstream versions of tools) so then its being figured out manually. See #2004 where the bot updates surelog but the CI fails, I assume exactly because of the changes that are needed in the plugin that you are trying to resolve here. Surelog on the other hand has a CI that tests if it breaks compatibility with the plugin so that such changes can be detected and avoided or mentioned here when there is an API change or some other reason that requires a plugin change. |
Fixed. |
Quick follow up - Doesn't look like current failure have anything to do with changes in this PR. Correct me if I am wrong. |
@hs-apotell the last merged PR has all tests passing: So this PR has issues. |
The logs with the failures are less than helpful to provide any indication of what/where it failed. I don't have a local setup to run yosys (I am on Windows platform). Can someone spare a few moments to debug the issue locally to provide some insight into the cause of the failures? Summary of what's attempted - All references to model objects of type |
b9274ae
to
c931103
Compare
@kgugala please add @hs-apotell as a contributor |
@hs-apotell , chipsalliance/Surelog#3872 fixed the failure on simple_AssignToUnionAndReadField, make -C tests uhdm/yosys/test-ast TEST=simple_tests/AssignToUnionAndReadField PARSER=surelog ... End of script. Logfile hash: d6346436ba, CPU: user 0.01s system 0.00s, MEM: 24.68 MB peak
|
It also fixes the 2 formal failures:
|
@kbieganski how to run locally this test: ❌ FAIL |
Done! Need someone to approve the workflows. |
Yes, hopefully @kgugala can add you as a contributor today so we can iterate over the week-end if there are still failures. |
@hs-apotell I've added you |
CI seems to be green now. @kbieganski please take look at this on Monday and review/merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed this. Let's merge it, it is blocking a lot of other work
I am confused, just use a branch? How is that a blocker? |
(@kbieganski is out of office today, he will be back on Monday and will look at it) |
I need this to be merged to my fork of this repo so I can attend to other failures. Can you accept this PR? It seems I don't have the rights to merge PR (no write access, only contributor). I work on weekends, delaying this prevent velocity. This PR is 100% correct. Or please add my rights to Write so I can merge after review which I can't now |
I do not have merge rights here, @kgugala can you merge? |
(@alaindargelas bear in mind its Friday evening here so no guarantees) |
Yes :-) Thanks guys, or @kbieganski might see and approve it. |
Sure, I'll merge this but I'd still prefer @kbieganski look at this and do proper public review |
Handle introduction of ref_typespec in UHDM/Surelog
chipsalliance/UHDM#1022
chipsalliance/Surelog#3868