-
Notifications
You must be signed in to change notification settings - Fork 177
Conversation
@jackkoenig do you know why the Chisel3 tests might be failing? I am going to rebase and see if it fixes anything, |
11ff055
to
f62336a
Compare
It's known flakiness (but unknown reason why), just restart the test |
f62336a
to
456d394
Compare
Seems like the Chisel test always exceeds its maximum length (+ it has all the broken pipe warnings). I did restart the tests twice by force pushing to the PR branch. |
456d394
to
c55c907
Compare
Travis is having issues and pulling resources away from their free open-source offering, that could be related. We probably need to switch to a different CI host anyway and perhaps that can at least workaround this issue. I'll poke around with Github Actions |
@Mergifyio backport 1.4.x |
* smt: add test for write port collision * smt: add missing call to insertDummyAssignsForMemoryOutputs * smt: fix typo in write port code Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 4c6993b) # Conflicts: # src/main/scala/firrtl/backends/experimental/smt/FirrtlToTransitionSystem.scala
Command
|
@Mergifyio backport 1.4.x |
Command
|
* smt: add test for write port collision * smt: add missing call to insertDummyAssignsForMemoryOutputs * smt: fix typo in write port code Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* smt: add test for write port collision * smt: add missing call to insertDummyAssignsForMemoryOutputs * smt: fix typo in write port code Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
This fixes two bugs in the SMT backend:
Contributor Checklist
Type of Improvement
API Impact
Backend Code Generation Impact
Desired Merge Strategy
Reviewer Checklist (only modified by reviewer)
Please Merge
?