Not accepting any donations until I have an actual release out there. I'll deal with all that stuff once the release is ready.
Respect !
Thank you for your efforts, very much appreciated.
Waiting for the release (and the donation address)
Topic: 0.94 preliminary testing phase - page 3. (Read 2790 times)
Respect !
Thank you for your efforts, very much appreciated.
Waiting for the release (and the donation address)
Not accepting any donations until I have an actual release out there. I'll deal with all that stuff once the release is ready.
You need a bitcoin address in your profile and sig here
I'm thinking this may also have to do with low disk space on my computer, so once I clean up some junk I will try again.
My DB is ~150MB on the mainnet. If you can't get it to scan mainnet, try the testnet, also build and run the C++ unit tests in the /cppForSwig/gtest folder and run those. Let me know if you can pass any of these and if you get errors, whether they are deterministic or random.
Can't wait thank you
Will you change the donation in it to you?
Will you change the donation in it to you?
Once I put out a release.
Quote
Will 0.94 be just these database changes and RBF signaling?
My plan is to put out a testing release after this phase. I'll go over all the PRs I have received and merge them in while I wait on feedback. Once I'm done with all DB bugs and PR merging, I'll release the rc1 and take it from there.
Great work! I will be testing this and will report back if anything bad happens.
Will 0.94 be just these database changes and RBF signaling?
Edit:
While armory was building the databases it crashed, twice now. I had renamed the old databases folder so armory create a new one for the new databases. This is the error that I got after both crashes:
I'm thinking this may also have to do with low disk space on my computer, so once I clean up some junk I will try again.
Will 0.94 be just these database changes and RBF signaling?
Edit:
While armory was building the databases it crashed, twice now. I had renamed the old databases folder so armory create a new one for the new databases. This is the error that I got after both crashes:
Code:
terminate called after throwing an instance of 'LMDBException'
what(): Failed to close env tx (Input/output error)
Aborted (core dumped)
Can't wait thank you
Will you change the donation in it to you?
Will you change the donation in it to you?
None. I've run it at least half a dozen times now, no segfaults so far. It does scan the wallet integrity twice, the second time after finishing the tx scan. Other than that it's in good shape on this platform.
No segfaults? How often have you ran it? Usually I consider 3 successful runs to be enough.
Code:
(DatabaseBuilder.cpp:47) updated HEADERS db in 4322.26s
Code:
(DatabaseBuilder.cpp:108) scanned new blocks in 2111.9s
All appears well with basic Db build and tx scan (other than the disconnected progress bars). Will test some more tomorrow.
Edit: testing with Haswell i5 laptop, Qubes 3.0/Xen 4.4, Debian 8.3, Bitcoin 0.11.2
sync'ing & building 
The new DB is about ready. It passes all C++ tests and runs *almost* fine. Turns out my own copy of the mainnet blockchain has a corrupt block (or at least some corner case that displays the same behavior), so I'll be taking extra time putting together a full diagnostic and repair code to get through that bad block. In the mean time I'd like some testing on what I have so far.
Haven't hooked the progress bars yet (so refer to your terminal/console output) but the rest should work (spends and ZC included). The code is in dev (https://github.com/goatpig/BitcoinArmory/tree/dev), pull away. I'm still pushing commits daily to that branch for now. Once it stabilizes and I put out the first testing builds, I'll move that code to a branch named testing.
If your scan fails please repeat and let me know if the error is random or deterministic.
EDIT: haven't tested rebuilds/rescans, they are probably broken. Delete the content of your DB folder manually if you want to rebuild. Obviously use a new folder (this db format is not compatible with ATI's 0.93/0.94 and coexist with it in the same folder). Expected DB size for mainnet is ~150MB.
Haven't hooked the progress bars yet (so refer to your terminal/console output) but the rest should work (spends and ZC included). The code is in dev (https://github.com/goatpig/BitcoinArmory/tree/dev), pull away. I'm still pushing commits daily to that branch for now. Once it stabilizes and I put out the first testing builds, I'll move that code to a branch named testing.
If your scan fails please repeat and let me know if the error is random or deterministic.
EDIT: haven't tested rebuilds/rescans, they are probably broken. Delete the content of your DB folder manually if you want to rebuild. Obviously use a new folder (this db format is not compatible with ATI's 0.93/0.94 and coexist with it in the same folder). Expected DB size for mainnet is ~150MB.
Jump to: