Port gHashTag/trinity:fpga/openxc7-synth/symbiflow_blink.v (Verilog, 1 module) to specs/port/trinity/fpga/openxc7-synth/ - #5663
Merged
Merged
Conversation
- Add xc7a100t_testbench module with 25-bit counter and LED output - Include constants, structs, and functions for counter behavior - Add comprehensive tests covering initialization, increment, overflow, LED output - Include invariants for compile-time validation - Benchmarks for performance measurement Closes #5655
A pull request must add exactly one docs/now entry and a bee has no way to know that: its brief names a boundary file and acceptance criteria, and docs/now/ is neither. The publisher adds it rather than failing the gate. Closes #5655 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
This was referenced Oct 3, 2026
specs/numeric: GF8/20/24/32 invariants check concrete points instead of prose the parser drops
#5699
Closed
specs/numeric: GF8/20/24/32 invariants check concrete points instead of prose the parser drops
#5702
Merged
Merged
This was referenced Oct 4, 2026
Merged
Closed
gHashTag
added a commit
that referenced
this pull request
Oct 4, 2026
#5853) * feat(tri pr ready): ask a check's own workflow when the commit window missed it `tri pr ready 5826` said CANNOT TELL (exit 3) on fpga-conformance: "did not run on any recent master commit". It had: master's newest run of FPGA E2E Build at e7ed379 failed that job, 21 commits back; the walk reads 15. Only for a failure neither the walk nor the merged-PR baseline observed: details_url -> run -> workflow -> its newest completed default-branch runs (page 10, page-fill guarded), read one at a time until a job of the same name reached success/failure/timed_out. Cancelled and skipped are passed over. Red there is pre-existing, green there is new here, nothing there stays NO BASELINE and says how far it looked. An API error leaves the check without a baseline: CANNOT TELL, never safe. The walk is unchanged. Real run: tri pr ready 5826 -> exit 0, citing e7ed379 and its age. 8 new tests (53 in prcheck), 7 mutations each red. Census: fetches moved 69 -> 72 lines, fetch sites 28 -> 31 (--paginate 7 -> 9, page-fill guarded 10 -> 11) -- the three new reads, every one complete or guarded; unguarded buckets unchanged. Blessed here. Closes #5837 Refs #5786 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(tri pr ready): --why compares what a pre-existing failure printed A check red on master under the same NAME was called pre-existing, whatever its step printed. A pull request that adds a fifth conflicted type name to the Corpus ratchet read exactly like one that adds nothing. --why (off by default) fetches the failing step's own output from both jobs -- this pull request's and the one the baseline used -- masks timestamps, colour codes, durations, shas and long ids, and compares each side's last 60 lines against the other side's whole output. A line not found as itself is looked for by its shape (digits read as #): it is printed for a person, not judged, because a count moves when the cause does not (#5663: observed 78 vs 81, a subset of master's names). NEW REASON is exit 7; precedence 2 > 3 > 1 > 7 > 0; --merge refuses. Live: #5781 NEW REASON (+ ModuleInterface), exit 7; #5663 SAME REASON, fewer, exit 0; #5812 NEW REASON (another step), exit 7. Tests: 6 new in prcheck::why_tests + the verdict test now calls the real verdict_code (59 in prcheck). 16 mutations, each red. Census: fetches 72 -> 74 lines, 31 -> 33 fetch sites, --paginate 9 -> 11 (failing_jobs_on, failing_job_in_run). Blessed here. Closes #5852 Refs #5837 #5839 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 4, 2026
Merged
This was referenced Oct 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #5655
Written by a bee on
queen-5655and published bytools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.🤖 Generated with Claude Code