Skip to content
Snippets Groups Projects
Select Git revision
  • fwd-compatible-with-future-gaudi-range-improvement
  • run5
  • mveghel-clustertrackmva
  • update-expected
  • tfulghes-p2p-relationtable-unpacker
  • release-v56r6
  • prefer-concepts
  • yitang/virtual_tag
  • wh_add_update_condition
  • master default protected
  • pytest-migration
  • mveghel-bremwithcharged
  • mstahl_tdps
  • tlatham_relatedinfomap_optional
  • ut-error-decoder
  • add-dependencies-versions-checks
  • SIMDWrapper-add-approx-log2-float
  • anmorris-higher-float_v-precision
  • run2-patches protected
  • caschbur_rich_make_pixels
  • v56r5
  • v55r14p1
  • v56r4
  • v46r9
  • v56r3
  • v55r16p2
  • v56r2
  • v55r13p2
  • v55r12p2
  • v55r11p2
  • reindentation
  • v38r2p4
  • v40r0p3
  • v55r16p1
  • v56r1
  • v55r17p1
  • v34r5
  • v32r4p1g2
  • v35r1p5
  • v41r5
40 results
Blame Permalink
  • Rosen Matev's avatar
    2813f008
    Fix event StatusCode after failure · 2813f008
    Rosen Matev authored 
    A successful event after a failed one got a failure StatusCode
because of how the AlgExecStateSvc works. An extra reset fixes that
problem.

By default we stop after the first failure.

Add a test to check skipping isolated events works (StopAfterNFailures > 1).
    2813f008
    History
    Fix event StatusCode after failure
    Rosen Matev authored 
    A successful event after a failed one got a failure StatusCode
because of how the AlgExecStateSvc works. An extra reset fixes that
problem.

By default we stop after the first failure.

Add a test to check skipping isolated events works (StopAfterNFailures > 1).
Code owners
Assign users and groups as approvers for specific file changes. Learn more.