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

Equivalence harness gaps that block the L1->L4 ladder: abend injection, SEND/RECEIVE/RETURN/SYNCPOINT/DELAY faults, CEEDAYS, X6 WRITEQ

Aperta
#6,271 4 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
24/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
devtools, testing

Direzione di ricerca

Read the equivalence harness and its fault/model assumptions, then inspect tests/equivalence/infeasible_outcomes.json and the #6072 programs cited for each gap. Start by choosing one checkbox-sized slice and tracing the relevant harness entry points and existing tests. Done means the harness records the fault or model, includes a test, and reports before/after coverage for the unblocked programs in the PR.

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

Descrizione

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

Why

The L1->L4 ladder (#6072) keeps ending at the same equivalence-harness limits rather than at missing scenarios: about 8 of the 33 ladder worker runs on 2026-10-22/23 stopped on one of the gaps below, and each run rediscovered it. Until the harness can inject or model these, the branches behind them can only be stated infeasible (when truly unreachable) or stay open.

Gaps (one checkbox = one slice; each cites the runs that hit it)

  • Abend injection: no way to make a called program / CICS command ABEND (incl. VSAM RLS abend) so HANDLE ABEND / abend paragraphs run (churn runs 6072-20261023T0128Z, 0354Z, 0448Z)
  • Failing SEND MAP / RECEIVE MAP / RETURN / SYNCPOINT: no RESP fault for these commands (0448Z)
  • DELAY fault (CBSA CRDTAGY1-5: the paragraphs behind a failed DELAY; 0128Z)
  • CEEDAYS model: CSUTLDPY date paragraphs in COACTUPC (90/95) need it (1553Z); stays within the CEEDAYS owner rulings (CRECUST stays refused)
  • Judging past an X6-refused WRITEQ (1701Z)
  • Paragraph-level infeasible outcomes in tests/equivalence/infeasible_outcomes.json (branch-level only today): CBPAUP0C 6000-EXIT was rediscovered in 5+ runs, CRDTAGY paragraphs stuck the same way (being added by the infeasible-outcomes tooling slice queued under #6072)

Acceptance

Each slice: the harness states the fault/model (oracle_assumptions entry where IBM documents the behaviour, refused by name where it does not), a test, and the #6072 programs it unblocks re-measured with before/after coverage in the PR body. Burned estates only; evidence levels, not "proven".

Part of #6072.

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

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.