Accept a custom scheduling strategy in ReplayRecordingOptions

Aperta
#77 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
54/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

Start by reading ReplayRecordingOptions, RecordCluster, and RecordClusterEntry, then trace how the scheduler strategy name and seed are written into the artifact. Check the replay recording tests for coverage of scheduler metadata. Done means an optional strategy factory can wrap the runtime's seeded strategy before the first step and the artifact records the resulting strategy's name.

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

Descrizione

ReplayRecordingOptions selects a built-in policy through ReplaySchedulingPolicy. A consumer which needs a custom ISimulationSchedulingStrategy must therefore assign SimulationScheduler.SchedulingStrategy inside the recorded callback. The artifact then names seeded-random as its strategy (scheduler.strategy, with its schedule seed), although every recorded decision came from the custom strategy. Exact replay still works, because it consumes the recorded decisions, but the artifact misdescribes the run that produced them.

Proposal. Add an optional strategy factory to ReplayRecordingOptions, for example Func<ISimulationSchedulingStrategy, ISimulationSchedulingStrategy>, which receives the runtime's seeded strategy so a custom strategy can delegate to it. Record the resulting strategy's Name in the artifact's scheduler section. RecordCluster and RecordClusterEntry would apply the factory before the first step.

Consumer. Clog's conformance kit (ReubenBond/clog#365) explores the schedules of small concurrent windows with WindowSchedulingStrategy. Inside a window it follows a choice vector, and outside every window it delegates to the seeded strategy. Today the driver swaps the strategy inside RecordCluster's callback.

Lingua principale
C#
Stelle
0
Fork
0
Merge medio
2h 32m
PR unite (30g)
23

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 ReubenBond/Clockwork

Tutte le issue di ReubenBond/Clockwork

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.