Skip to content

Dev config: logix-core 2026-11-15 (openXC7 2026-11-15); drop the apio#1194 CI workaround - #4

Merged
zapta merged 2 commits into
mainfrom
dev-config-core-2026-11-15
Nov 15, 2026
Merged

zapta merged 2 commits into
mainfrom
dev-config-core-2026-11-15

Conversation

@zapta

@zapta zapta commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

Points the dev channel's logix-core at 2026-11-15, which has openXC7 2026-11-15 (logix-core 8f17d0a). That openXC7 fixes:

  • apio#1192: Xilinx resource counts.
  • apio#1194: Windows Python. Its launchers now find a Python themselves.

It also removes the CI-only workaround for apio#1194 (a system Python 3.12 put on the tools' PATH), from test.yaml and build-windows-x86-64.yaml, and its mention in CLAUDE.md. So the Windows Xilinx tests (builds_a_xilinx_design, program_board_refuses_a_board_with_another_fpga, designs_without_logic_build) now pass only if openXC7 finds OSS CAD Suite's own Python.

Only dev.jsonc changes among the configs, so prod is unaffected.

🤖 Generated with Claude Code

zapta and others added 2 commits November 15, 2026 09:14
…#1194 CI workaround

openXC7 2026-11-15 counts Xilinx resources right (apio#1192) and its
Windows launchers find a Python themselves (apio#1194): with the engine's
tool PATH, OSS CAD Suite's lib\python3.exe. So the CI-only steps that put
a system Python 3.12 on that PATH go, in the tests and the Windows build,
and the Windows Xilinx tests now check the upstream fix itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI sets LOGIX_ENGINE_CHANNEL for each channel's job, so the catalog
folder isn't always the first developer setting.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@zapta
zapta merged commit a05b6ba into main Nov 15, 2026
14 checks passed
@zapta
zapta deleted the dev-config-core-2026-11-15 branch November 15, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant