Topic: Please test (if you dare): next-test 2012-06-21 (Read 2305 times)
keeps crashing every few hours.
Win7-x64
Win7-x64
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: bitcoin-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 4d44aa00
Fault Module Name: bitcoin-qt.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4d44aa00
Exception Code: c0000005
Exception Offset: 0007ccf4
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Why is this client creating a new testnet wallet, and not using the existing one?
Because the old testnet is being obsoleted.
0.7.0 (and the current code in git, and this next-test branch) will use "testnet3", a completely reset version. Testnet2 has undergone two many changes, and too many incompatible chains exist on the network. They were very valuable to learn from, but not really usable for real tests.
Why is this client creating a new testnet wallet, and not using the existing one?
Luke, thanks for the reply... The transaction just got through.
Transaction ID: d0fb364098148670d55a414d060eaba8e9b9e74c67c79687d05e8184ef2d92ba
Transaction ID: d0fb364098148670d55a414d060eaba8e9b9e74c67c79687d05e8184ef2d92ba
EDIT: I don't know if it's a bug... I sent 0.01 BTC to another address and even after 2 hours, still no confirmation. No signs of the transaction on blockchain.info although the amount has been deducted from the wallet. Any clues?
Transaction id?
To make it more user friendly when selecting a display language, I suggest putting words (English, Greek, etc) instead of codes (en, el_gr, etc).
I like in this release the ability to verify a message, that is missing from the official client.
Wasn't it supposed to ask me from which address I would like to send BTC from, when sending to others? As far as I remember, this is part of the Coin Control. Had to enable the option.
This is as much as I can test for now. Keep up the good work!
EDIT: I don't know if it's a bug... I sent 0.01 BTC to another address and even after 2 hours, still no confirmation. No signs of the transaction on blockchain.info although the amount has been deducted from the wallet. Any clues?
I like in this release the ability to verify a message, that is missing from the official client.
This is as much as I can test for now. Keep up the good work!
EDIT: I don't know if it's a bug... I sent 0.01 BTC to another address and even after 2 hours, still no confirmation. No signs of the transaction on blockchain.info although the amount has been deducted from the wallet. Any clues?
I'll get this compiled later today or tomorrow.
How to test ?please tell me
next-test is a branch of the mainline bitcoind & Bitcoin-Qt with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details).
Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLET
Today's next-test includes the following pull requests (green are merged now; red are disputed):
- IPv6 RPC using asynchronously accepted connections
- Parse URIs with non-BTC amounts
- -acceptnonstdtxn option to skip "non-standard transaction" checks
- Optimized binary-to-hex converter (ToHex)
- FastGetWork optimization
- Specify fees explicitly via JSON-RPC
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
- BIP22: getmemorypool
- Stop processing messages on full send buffer and dont disconnect.
- New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined
- massive URI-handling / IPC server re-work
- Relay and accept transactions that personally benefit the user
- Tor hidden service support
- Buffer block downloading and commit/check blocks in parallel
- Refactor CreateNewBlock transaction selection algorithm
- Bugfix: getwork/getmemorypool: NULL pindexPrev across CreateNewBlock, in case it fails
- CreateNewBlock: Check that the produced CBlock is acceptable
- Issue1234
- Show block timestamp
- Add -proxytoo option, which allows proxy use non-exclusively, unlike the -proxy option.
- Quieter initial block download
- Who doctored.... never was very useful, now only for the debuggers...
- Show when node is misbehaving, not just at the point that it gets banned...
- mapAlreadyAskedFor gets additions when AlreadyHave()
- getmemorypool: longpolling support
- Coin Control
- Refactor transaction/accounting time
- Make truncating the debug.log file an option.
- CHub Rev. 3
- Treat generation (mined) transactions less different from receive transactions
- Show more significant bytes of block hashes.
- No need to log start time if it's already being done on every line.
- Cblockstore class
- Make IPv6 support optional again (defaults to enabled)
- Implement raw transaction RPC calls
- Introduce -tracenet option, thereby quieting some redundant debug messages
- GUI: show used OpenSSL library version in about dialog
- write used OpenSSL library version to debug.log
- GUI: merge sign/verify message into a single window with tabbed UI
- Add new P2P command and response: "getcmds", "cmdlist"
- walletmodel: only update cached balances / transaction numbers and emit ...
- add CWalletTx::GetImmatureCredit() and use it in CWallet::GetImmatureBalance()
- Document Gitian build process for Mac OS X bitcoind binary
- Skip tons of duplicate GetHash() calls in Block Commit Thread
- RPC: lock push-down, preparing for parallelization opportunities
- fix a memory leak in key.cpp
- CBigNum: Convert negative int64 values in a more well-defined way
- Add support for a cjdns network type
Bugs found:
- Bad use of global variable
- Another bad use of global
- Merged sign/verify message dialog build failure
- askfor formatting build failure
- File addition missing in Bitcoin-Qt project
- Advertising mempool transactions needs some way to fetch them
- Messed up branch for concurrent block downloading
- Omitting start time with timestamps doesn't build
- Smart times always displayed as 1970
- IPv6 RPC needs to add library to Win32 build
- Bitcoin-Qt build was disabling IPv6 by default
5JiDHgjbkS2uKnMKHo1Nw8zrJp2t8wZ4QmJPFi9W9DQjjFgYFG7
Jump to: