de/serialize: round-trip test sometimes fails
See original GitHub issueIt’s not consistent, but the I’ve seen the “de/serialize: round-trip” test in stream-deserialize.test.js fail several times:
# de/serialize: round-trip
ok 216 null
not ok 217 round-tripped mbtiles are approx. the same size
---
operator: ok
expected: true
actual: false
at: Put.makeAssertions (/builddir/build/BUILD/tilelive-5.11.0/test/stream-deserialize.test.js:189:11)
...
I assume the threshold is maybe a bit too tight and, depending on environmental details, it may be exceeded?
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
c# - How to unit test if my object is really serializable?
Deserialize the results back to a new object and make sure the two instances are equivalent. Share.
Read more >Round trip fuzz tests | Distilled Derivatives
Some cute round trip test tricks. In the last post, we looked at layering our deserialization code to keep things simple.
Read more >Tests silently fail when custom test cases fail to deserialize ...
The issue ended up being that our custom test cases weren't able to be serialized/deserialized. In the end this manifested as tests not...
Read more >Serialization and Deserialization - WCF - Microsoft Learn
A round trip occurs when an object is deserialized and re-serialized in one operation. Thus, it goes from XML to an object instance, ......
Read more >Failed to deserialize error when running unit test - Development
I noticed that was because in my dataset file I was adding an obs which did not exist. Once I fixed that and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We can certainly adjust this threshold. A better test would be one that actually asserts that the tile data itself successfully navigates the roundtrip through serialization.
This test has been rewritten and is now part of version
5.12.5#195