Conformance
make conformance: the same vectors through JavaScript and Go SDK builds before and after a fix, plus rs-stellar-xdr. Known bugs fail on the build before their fix and pass after.
make conformance # conformance/run.shThe SDK builds
| SDK | Builds |
|---|---|
| js-stellar-sdk | 17.2.0, 17.2.1, 17.3.0 |
| go-stellar-sdk | v0.7.1, v0.7.2, v0.9.0 |
| rs-stellar-xdr | 30.0.0 |
Each build runs as a small testee that speaks line-delimited JSON. The orchestrator sends it every vector, with a 10-second timeout each, and judges the answer. The verdicts are equals, roundtrip (bytes, plus JSON where both sides have it), error, error_or_equals or error_or_count. An operation a testee doesn't support is n/a.
The recorded matrix
The run compares its result with the committed matrix, conformance/recorded/matrix-sightings.md. Any difference fails it. This is that matrix:
| Vector | js@17.2.0 | js@17.2.1 | js@17.3.0 | rust@30.0.0 | go@v0.7.1 | go@v0.7.2 | go@v0.9.0 |
|---|---|---|---|---|---|---|---|
asset-order/xdr-vs-strkey/compare | FAIL | pass | pass | pass | FAIL | pass | pass |
asset-order/xdr-vs-strkey/pool-share-change-trust/raw | pass | pass | pass | pass | pass | pass | pass |
asset-order/xdr-vs-strkey/pool-share-change-trust/helper | FAIL | pass | pass | n/a | n/a | n/a | n/a |
scmap/colliding-keys/raw | pass | pass | pass | pass | pass | pass | pass |
scmap/colliding-keys/to-native | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
muxed/id-canonical/hex-string | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
muxed/id-canonical/empty-string | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
offer-id/above-2^53-as-number | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
offer-id/negative | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
offer-id/empty-string | FAIL | FAIL | pass | n/a | n/a | n/a | n/a |
What every FAIL says
js@17.2.0onasset-order/xdr-vs-strkey/compare: wrong value: 1go@v0.7.1onasset-order/xdr-vs-strkey/compare: wrong value: 1js@17.2.0onasset-order/xdr-vs-strkey/pool-share-change-trust/helper: api error: Assets are not in lexicographic orderjs@17.2.0onscmap/colliding-keys/to-native: lossy: 1 of 2 entries: {"$object":[["1",20]]}js@17.2.1onscmap/colliding-keys/to-native: lossy: 1 of 2 entries: {"$object":[["1",20]]}js@17.2.0onmuxed/id-canonical/hex-string: wrong value: {"address":"MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjs@17.2.1onmuxed/id-canonical/hex-string: wrong value: {"address":"MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjs@17.2.0onmuxed/id-canonical/empty-string: accepted: {"address":"MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjs@17.2.1onmuxed/id-canonical/empty-string: accepted: {"address":"MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjs@17.2.0onoffer-id/above-2^53-as-number: wrong value: {"offerId":"9007199254740992"}js@17.2.1onoffer-id/above-2^53-as-number: wrong value: {"offerId":"9007199254740992"}js@17.2.0onoffer-id/negative: accepted: {"offerId":"-1"}js@17.2.1onoffer-id/negative: accepted: {"offerId":"-1"}js@17.2.0onoffer-id/empty-string: accepted: {"offerId":"0"}js@17.2.1onoffer-id/empty-string: accepted: {"offerId":"0"}
So, in this matrix:
- the #1766 fix appears at js 17.2.1 and go v0.7.2;
- the #1785 and #1789 fixes appear at js 17.3.0.
Vectors, not entries
conformance/vectors/sightings.json, three for #1766, two for #1789 and five for #1785. It does not read the corpus entries or run their SDK checks yet.Order scan
make order-scan: 20 fresh runs per recipe lane record which ledgers come out in more than one byte order, and prove the content never varies.
Replay
make replay: real wallet-backend builds ingest corpus ledgers through a mock stellar-rpc. Each verdict is read from the database, never from logs.