ESP-IDF CI / Host Tests (Unity) (push) Successful in 1m8s
CI / firmware-native (push) Successful in 2m57s
Rust Protection Tests / Cargo test (host) (push) Failing after 3m21s
ESP-IDF CI / ESP-IDF Build (v5.4) (push) Failing after 6m55s
ESP-IDF CI / Memory Budget Gate (push) Has been skipped
qa-cicd-environments / qa-kxkm-s3-build (push) Successful in 8m53s
qa-cicd-environments / qa-sim-host (push) Successful in 2m2s
qa-cicd-environments / qa-kxkm-s3-memory-budget (push) Successful in 11m17s
Context: the project archive (KXKM_Batterie_Parallelator-main) had no git history locally; a fresh repository is needed to host it on git.saillant.cc (electron/KXKM_Batterie_Parallelator). Approach: initialize a new repo on branch main, stage the archive content, and harden .gitignore before the first commit. Changes: - Import the full project tree: firmware/, firmware-idf/, firmware-rs/, iosApp/, kxkm-bmu-app/, kxkm-api/, hardware/, docs/, specs/, scripts/, models/, tests/ - Keep project dotfiles tracked despite the trailing '.*' ignore rule: .github/, .claude/, .superpowers/, .gitattributes, .markdownlint.json - Extend .gitignore: firmware/src/credentials.h (local secrets, template kept), kxkm-bmu-app/**/build/ (66 MB compiled iOS framework), .remember/ (session data) Impact: the project can now be maintained on the self-hosted Gitea forge with a clean, secret-free initial history.
1.9 KiB
1.9 KiB
QA CI/CD par environnement
Statut: local OK, preuve distante en attente d’activation/présence du workflow sur la branche par défaut.
Objectif
- Exécuter QA de manière déterministe par environnement (
sim-host,kxkm-s3-build,kxkm-v3-build,kxkm-s3-memory-budget). - Capturer des preuves exploitables localement et côté GitHub Actions.
Exécution locale
bash scripts/ci/run_qa_all.sh
Commande équivalente par environnement:
bash scripts/ci/run_qa_env.sh sim-host
bash scripts/ci/run_qa_env.sh kxkm-s3-build
bash scripts/ci/run_qa_env.sh kxkm-v3-build
bash scripts/ci/run_qa_env.sh kxkm-s3-memory-budget
Preuve distante GitHub Actions
- Vérifier les workflows disponibles:
gh workflow list --repo KomplexKapharnaum/KXKM_Batterie_Parallelator
- Si le workflow
qa-cicd-environmentsexiste et exposeworkflow_dispatch, le déclencher:
gh workflow run qa-cicd-environments --ref object-orriented --repo KomplexKapharnaum/KXKM_Batterie_Parallelator
- Exporter une table de preuves:
bash scripts/ci/collect_remote_qa_evidence.sh qa-cicd-environments object-orriented 10
Blocage connu (2026-03-29)
- Le fichier
.github/workflows/sim-host-tests.ymln’existe pas encore sur la branche par défaut distante. - Le workflow
CIdistant ne possède pas de triggerworkflow_dispatch. - Prochaine action: pousser/ouvrir PR contenant le workflow
qa-cicd-environments, puis relancer la collecte de preuves.
Automatisation de preuve distante (nouveau)
Commande:
bash scripts/ci/request_remote_qa_proof.sh \
KomplexKapharnaum/KXKM_Batterie_Parallelator \
object-orriented \
qa-cicd-environments \
docs/QA_REMOTE_PROOF_LATEST.md
Résultat actuel: un snapshot horodaté est produit dans docs/QA_REMOTE_PROOF_LATEST.md avec inventaire workflows, runs disponibles, diagnostic dispatch, et prochaine action.