fix(telemetry): match the renamed close-time attrs in expected_spans.json

The close-time span attributes name their unit and epoch:
close_time_ripple_epoch_s, parent_close_time_ripple_epoch_s and
close_time_self_ripple_epoch_s. The harness inventory still required the
unsuffixed keys, so the attribute checks for consensus.accept.apply and
ledger.build failed on every validation run while the spans themselves
were correct.

Rename the four required_attributes entries to the keys the code emits.
This commit is contained in:
Pratik Mankawde
2026-09-04 11:47:33 +01:00
parent 8900060979
commit f80faea85d

View File

@@ -235,9 +235,9 @@
"parent": "consensus.accept",
"required_attributes": [
"ledger_seq",
"close_time",
"parent_close_time",
"close_time_self",
"close_time_ripple_epoch_s",
"parent_close_time_ripple_epoch_s",
"close_time_self_ripple_epoch_s",
"close_time_vote_bins",
"resolution_direction"
],
@@ -288,7 +288,7 @@
"parent": null,
"required_attributes": [
"ledger_seq",
"close_time",
"close_time_ripple_epoch_s",
"close_time_correct",
"close_resolution_ms"
],