features-coverage

Workflow runs for features-coverage

• node-sync ve los jobs, mira a todos los workers de la cola, y su timer arranca aunque se instale tarde

  completed successfully:
  features-coverage#92:Pull request#349openedbyfrapercan
  fix/node-sync-jobs-en-vuelo

  Oct 8, 20269s
  More actions for workflow run 92

• An archive is not publishable prose

  completed successfully:
  features-coverage#91:Pull request#305openedbyfrapercan
  fix/un-archivo-no-es-prosa-publicable

  Sep 14, 20266s
  More actions for workflow run 91

• node: the sync guard managed one unit and reported on the node

  completed successfully:
  features-coverage#90:Pull request#291synchronizebyfrapercan
  node/sync-manages-every-unit

  Sep 12, 202610s
  More actions for workflow run 90

• node: the sync guard managed one unit and reported on the node

  completed successfully:
  features-coverage#89:Pull request#291openedbyfrapercan
  node/sync-manages-every-unit

  Sep 7, 202612s
  More actions for workflow run 89

• node: retire the throughput sampler, and say what replaces it

  completed successfully:
  features-coverage#88:Pull request#286openedbyfrapercan
  node/retire-throughput-sampler

  Sep 4, 202610s
  More actions for workflow run 88

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#87:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20269s
  More actions for workflow run 87

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#86:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 202612s
  More actions for workflow run 86

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#85:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20269s
  More actions for workflow run 85

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#84:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20266s
  More actions for workflow run 84

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#83:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20269s
  More actions for workflow run 83

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#82:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20268s
  More actions for workflow run 82

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#81:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 2, 20267s
  More actions for workflow run 81

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#80:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 1, 20267s
  More actions for workflow run 80

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#79:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 1, 20269s
  More actions for workflow run 79

• The design phase, written down before a session limit costs it again

  failed:
  features-coverage#78:Pull request#271synchronizebyfrapercan
  plans/clean-campaign-design-state

  Sep 1, 202612s
  More actions for workflow run 78

• The compute node follows what the server declares

  completed successfully:
  features-coverage#77:Pull request#263openedbyfrapercan
  feat/the-compute-node-follows-what-the-server-declares

  Aug 30, 20269s
  More actions for workflow run 77

• The worker waits for a synchronised clock before it consumes

  completed successfully:
  features-coverage#76:Pull request#261openedbyfrapercan
  node/the-worker-waits-for-the-clock

  Aug 29, 20267s
  More actions for workflow run 76

• feat(services): the compute node configures itself from one script

  failed:
  features-coverage#75:Pull request#260synchronizebyfrapercan
  feat/compute-node-setup

  Aug 29, 20268s
  More actions for workflow run 75

• feat(services): the compute node configures itself from one script

  failed:
  features-coverage#74:Pull request#260openedbyfrapercan
  feat/compute-node-setup

  Aug 29, 20269s
  More actions for workflow run 74

• fix(services): the workers serve from a deploy slot, not from whoever is editing

  completed successfully:
  features-coverage#73:Pull request#251synchronizebyfrapercan
  fix/worker-serves-from-deploy-slot

  Aug 28, 20267s
  More actions for workflow run 73

• fix(services): the workers serve from a deploy slot, not from whoever is editing

  failed:
  features-coverage#72:Pull request#251synchronizebyfrapercan
  fix/worker-serves-from-deploy-slot

  Aug 28, 20268s
  More actions for workflow run 72

• fix(services): the workers serve from a deploy slot, not from whoever is editing

  completed successfully:
  features-coverage#71:Pull request#251openedbyfrapercan
  fix/worker-serves-from-deploy-slot

  Aug 20, 20268s
  More actions for workflow run 71

• plan: make the ladder a claim something can refuse

  completed successfully:
  features-coverage#70:Pull request#248synchronizebyfrapercan
  plan/rung-declaration

  Aug 20, 20267s
  More actions for workflow run 70

• plan: make the ladder a claim something can refuse

  completed successfully:
  features-coverage#69:Pull request#248synchronizebyfrapercan
  plan/rung-declaration

  Aug 20, 202610s
  More actions for workflow run 69

• plan: make the ladder a claim something can refuse

  failed:
  features-coverage#68:Pull request#248synchronizebyfrapercan
  plan/rung-declaration

  Aug 20, 20266s
  More actions for workflow run 68