-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a few more tests for book #1275
base: master
Are you sure you want to change the base?
Conversation
I saw this with @prometheus also, so can confirm the first 2 also. I don't understand the 3rd thing tho? Note to others: Book + the RAD updates are being coded on a "rebuild the plane while flying" path. We're first testing whether parts "fit" together, even when we know they don't work. If the scaffold fits, it does nothing / behaves incorrectly at first, but then we filling in the engine. Its like replacing a black box system. |
An approximate summary of the third issue:
If I use a new rad for the reads, the values are retrieved correctly.
Or, if the values are large enough to split into their own file, they are both retrieved correctly.
So it seems like the in-memory data vs. the on-disk data have some disagreements, but surprisingly to me the on-disk data is more correct. |
oof. |
Not sure if it matters, but might be important:
Thought I might be able to get the second write to work by re-reading what's on disk, but no. |
I'm back from a bunch of conferences... let's resume / catch up. DM me on twitter some times to do a screen call. |
A few new tests and a little more test tooling for book.
A few failures that are interesting:
'
and|
in the word failsI believe these bugs encompass most of the failures in the tests, and I've tried to add FIXMEs in the tests that most effectively illustrate them. Some of the TODOs are for me. Again, I plan on cleaning this file up at some point but the test failures aren't doing much good sitting on my machine and I'm not 100% sure when I'll be able to get back to it.