Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Equivalence harness gaps 3: CBSA fault injection and CardDemo L3 diagnosis (ladder tail, Part of #6072)

Aperta
  • Qualcosa non va?
#6,967 10 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
devtools, testing

Direzione di ricerca

Start with the equivalence harness changes in #6994 and #7001, then inspect the #6072 run results and the named CBSA and CardDemo programs. Identify the untaken branches and determine whether each needs a scenario, fault injection, or an owner ruling; follow IBM's documented semantics and state assumptions. Done means harness/runtime gaps are fixed in one class per PR, while data-only work goes to #6072 and uncertain outcomes are raised for an owner ruling.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

claim:melek enhancement legacy-modernization priority: high scope:core testing

Why

#6882 (harness gaps 2) is closed, and the ladder tail outside cics-crucible (L1 skipped by the owner, 2026-10-28) is held by code, not data. Recent #6072 runs end with "no PR" for these reasons. This issue collects them so churn has code work to do instead of data-only slices that cannot move. Numbers from churn goal status, 2026-10-29T00:59Z.

CBSA (4 at L3: BNK1CAC, BNK1CCS, BNK1DCS, CRECUST)

From run 6072-20261028T1058Z: all 14+ open outcomes need harness code or an owner ruling.

  • Harness: a fault command for TERMINAL operations (the SEND / RECEIVE outcomes the CBSA BMS programs branch on) (#6994)
  • Harness: FETCH ANY, container, ENQ and CEELOCT fault injection (#7001)
  • Harness: abend injection where the outcomes follow #6884
  • BNK1CAC: the 437 DEEDIT gap. List the X8 refusals it hits and write the owner question up here if a ruling is needed. Do not guess.
  • CRECUST: confirm what holds it at L3 under the 2026-10-27 slack-bytes ruling (X'40', CRECUST only)

CardDemo (4 at L3: CBPAUP0C, COACCT01, CODATE01, CSUTLDTC)

No blocker is recorded yet. Last measured net branch coverage: CSUTLDTC 40.0, CODATE01 15.4, COACCT01 12.9 (CBPAUP0C newly at L3).

  • Diagnose each one: which net branches are untaken, and whether a scenario (data), a harness fault, or a reviewed infeasible outcome closes each. Fix the harness / runtime part here; data-only closures go to #6072.

Rules

Burned estates only. Follow IBM's documented semantics and state every assumption. One class per PR, "Part of #6072". Siblings go into this issue rather than a new one. An owner ruling is asked here, not guessed.

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 14m
PR unite (30g)
967

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.