Repository navigation
ci: 挂 GitHub Actions —— 首份 CI(必过 job + 不阻断的 embedding job) - #2
Merged
Merged
Conversation
本仓此前没有任何 CI(gh pr checks → no checks reported)。
- job test(必过):PG(pgvector:pg16) + Redis 服务容器 → psql -f schema.sql 建表
→ pytest -m "not requires_ollama"(39 用例)
- job test-embedding(continue-on-error):装 Ollama + 拉 bge-m3
→ pytest -m requires_ollama(13 用例)
- pytest.ini 注册 requires_ollama 标记;test_day18 / test_day19 各加 pytestmark
(day19 原本没有 import pytest,一并补上,否则 collection NameError)
- 本地已验证两条选择:39 passed / 13 deselected,13 passed / 39 deselected
提交前两问
① 本次有决策事项 ⇒ 已建 DEC:docs/decisions决策/DEC-002-CI的embedding边界-20260921.md
(「CI 怎么覆盖 embedding 用例」三选一:单 job 全跑 / 只跑不依赖的 /
两个 job + 后者不阻断 → 选定第三种,理由与反悔成本见该文档)
② CHANGELOG 已写:CHANGELOG.md(第 2 轮)
注:CI 里的 PG 口令是刻意的公开值(一次性容器、runner 内网),真环境凭据一律走 .env。
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
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.
本仓此前没有任何 CI(
gh pr checks→no checks reported)。两个 job
testpsql -f schema.sql建表 →pytest -m "not requires_ollama"(39 用例)test-embeddingbge-m3→pytest -m requires_ollama(13 用例)continue-on-error)为什么 embedding 那个 job 不阻断:GitHub runner 只有 CPU,1.2 GB 模型走 CPU 很慢;且
test_day19是性能断言(KV≤Ledger、RAG>KV),在共享 runner 上噪声大 ⇒ 天然 flaky。详见docs/decisions决策/DEC-002-CI的embedding边界-20260921.md(含三个备选方案的对比与反悔成本)。顺带
pytest.ini注册requires_ollama标记;test_day18/test_day19各加一行pytestmarktest_day19原本没有import pytest—— 不加会 collection 直接 NameError,已补pytest -m "not requires_ollama"→ 39 passed / 13 deselectedpytest -m requires_ollama→ 13 passed / 39 deselected两点说明
ci_only_ephemeral):一次性容器、只活在 runner 内网,不是机密。真环境凭据一律走.env(不入库)。psql -f schema.sql建表 —— 这使schema.sql从"导出的副产品"变成 CI 的硬依赖。提交前两问
① 有决策事项 ⇒ 已建
DEC-002(三选一:单 job 全跑 / 只跑不依赖的 / 两个 job + 后者不阻断 → 选定第三种)② CHANGELOG 已写(第 2 轮)