Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: Luke-Jr on May 20, 2012, 02:48:37 PM



Title: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on May 20, 2012, 02:48:37 PM
Superceded with next-test 2012-06-21 (https://bitcointalk.org/?topic=89099)

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

  • Windows: installer (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120519/bitcoin-next-test-20120519-win32-setup.exe) ‖ zip (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120519/bitcoin-next-test-20120519-win32.zip) (sigs (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120519/SHA256SUMS.asc))
  • Source code: git (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/shortlog/refs/tags/next-test_20120519) ‖ tar.gz (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20120519.tar.gz) ‖ zip (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20120519.zip)

Today's next-test includes the following pull requests (green are merged now; red are disputed):
  • Parse URIs with non-BTC amounts (https://github.com/bitcoin/bitcoin/pull/553)
  • -acceptnonstdtxn option to skip "non-standard transaction" checks (https://github.com/bitcoin/bitcoin/pull/559)
  • Optimized binary-to-hex converter (ToHex) (https://github.com/bitcoin/bitcoin/pull/562)
  • FastGetWork optimization (https://github.com/bitcoin/bitcoin/pull/565)
  • Specify fees explicitly via JSON-RPC (https://github.com/bitcoin/bitcoin/pull/570)
  • Reopen log file on SIGHUP (https://github.com/bitcoin/bitcoin/pull/917)
  • Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC) (https://github.com/bitcoin/bitcoin/pull/929)
  • BIP22: getmemorypool (https://github.com/bitcoin/bitcoin/pull/936)
  • New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined (https://github.com/bitcoin/bitcoin/pull/989)
  • URI-handling code update - safety check and notification (https://github.com/bitcoin/bitcoin/pull/1002)
  • massive URI-handling / IPC server re-work (https://github.com/bitcoin/bitcoin/pull/1023)
  • Relay and accept transactions that personally benefit the user (https://github.com/bitcoin/bitcoin/pull/1128)
  • Trim trailing whitespace in src/*.{cpp,h} (https://github.com/bitcoin/bitcoin/pull/1170)
  • Tor hidden service support (https://github.com/bitcoin/bitcoin/pull/1174)
  • Fine-grained UI updates (https://github.com/bitcoin/bitcoin/pull/1205)
  • Refactor CreateNewBlock transaction selection algorithm (https://github.com/bitcoin/bitcoin/pull/1240)
  • Bugfix: getwork/getmemorypool: NULL pindexPrev across CreateNewBlock, in case it fails (https://github.com/bitcoin/bitcoin/pull/1245)
  • CreateNewBlock: Check that the produced CBlock is acceptable (https://github.com/bitcoin/bitcoin/pull/1246)
  • Issue1234 (https://github.com/bitcoin/bitcoin/pull/1271)
  • Signbugs (https://github.com/bitcoin/bitcoin/pull/1298)
  • Reorganize(): remove spurious TxnAbort() (https://github.com/bitcoin/bitcoin/pull/1300)
  • Get rid of snprintf (except one) with fixed buffers, shorten code (https://github.com/bitcoin/bitcoin/pull/1302)
  • Show block timestamp (https://github.com/bitcoin/bitcoin/pull/1304)
  • Add -proxytoo option, which allows proxy use non-exclusively, unlike the -proxy option. (https://github.com/bitcoin/bitcoin/pull/1306)
  • translation updates / string updates (https://github.com/bitcoin/bitcoin/pull/1323)
  • Filter out whitespace and zero-width non-breaking spaces in address field validator (https://github.com/bitcoin/bitcoin/pull/1329)
  • Who doctored.... never was very useful, now only for the debuggers... (https://github.com/bitcoin/bitcoin/pull/1339)
  • Should not be T minus, as this indicate duration to future event. (https://github.com/bitcoin/bitcoin/pull/1342)
  • Unless debugging, show a more useful format for the askfors (https://github.com/bitcoin/bitcoin/pull/1344)
  • mapAlreadyAskedFor gets additions when AlreadyHave() (https://github.com/bitcoin/bitcoin/pull/1347)
  • ECDSA signature optimization and more DoS prevention (https://github.com/bitcoin/bitcoin/pull/1349)
  • RPC: add client startuptime to RPC getinfo (https://github.com/bitcoin/bitcoin/pull/1352)
  • GUI: add an icon for Debug logfile -> Open in the RPC console (https://github.com/bitcoin/bitcoin/pull/1353)
  • Update Header Licenses (https://github.com/bitcoin/bitcoin/pull/1354)
  • getmemorypool: longpolling support (https://github.com/bitcoin/bitcoin/pull/1355)
  • Coin Control / less change / refactor coin selection (https://github.com/bitcoin/bitcoin/pull/1359)
  • remove strncasecmp() + strnicmp() calls use boost::algorithm::istarts_with() (https://github.com/bitcoin/bitcoin/pull/1363)


Title: Re: Please test (if you dare): next-test 20120519
Post by: R- on May 20, 2012, 03:48:02 PM
Could you make one thread?


Title: Re: Please test (if you dare): next-test 20120519
Post by: BCB on May 20, 2012, 04:18:59 PM
Error: Couldn't open socket for incoming connections (socket returned error 10047)


Title: Re: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on May 20, 2012, 04:48:04 PM
Error: Couldn't open socket for incoming connections (socket returned error 10047)
Try -onlynet=IPv4


Title: Re: Please test (if you dare): next-test 20120519
Post by: BCB on May 20, 2012, 05:18:38 PM
worked.


Title: Re: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on May 20, 2012, 06:35:41 PM
worked.
Can you detail your OS version and system configuration?


Title: Re: Please test (if you dare): next-test 20120519
Post by: BCB on May 20, 2012, 06:41:49 PM
XP Pro 2002 SP3


Title: Re: Please test (if you dare): next-test 20120519
Post by: Pieter Wuille on May 20, 2012, 06:54:58 PM
Error: Couldn't open socket for incoming connections (socket returned error 10047)

Is that error fatal?


Title: Re: Please test (if you dare): next-test 20120519
Post by: BCB on May 20, 2012, 07:04:42 PM
No. 

https://i.imgur.com/TvKXj.png

I clicked ok and the client opened out of sync.  I think it might have synced when the block chain downloaded.

After your message. I created a default bitcoin.conf in \Application Data\bitcoin and added
onlynet=IPv4

and it opened fine after restart.

I haven't tried any other actions.


Title: Re: Please test (if you dare): next-test 20120519
Post by: bitlane on May 22, 2012, 05:00:17 AM
Quote
getmemorypool: longpolling support

Does this mean longpolling for solo mining ?

Would it be beneficial to try this build for solo mining, or is this more intended for every day wallet use 'testing' ?


Title: Re: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on May 22, 2012, 05:51:54 AM
Quote
getmemorypool: longpolling support
Does this mean longpolling for solo mining ?
Only with a getwork server in between, like Eloipool or P2Pool - but neither of them support longpolling yet (unless Forrest has already added it).

Would it be beneficial to try this build for solo mining, or is this more intended for every day wallet use 'testing' ?
Compared to all the released versions, this build might perform better for (direct) solo mining due to the multithreaded JSON-RPC server (already merged into git master, so not listed specifically for next-test).


Title: Re: Please test (if you dare): next-test 20120519
Post by: Red Emerald on May 22, 2012, 06:46:25 AM
Got a bitcoind tor hidden service running with -discover

p2hwc26zdsrqxiix.onion

Seems to be running great! I'll send some transactions to/from it soon.


Title: Re: Please test (if you dare): next-test 20120519
Post by: pc on May 29, 2012, 02:18:36 AM
Is there any chance of getting a Mac build of these tests?


Title: Re: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on May 29, 2012, 02:20:01 AM
Is there any chance of getting a Mac build of these tests?
That would be one result of my deterministic Mac binaries (https://bitcointalk.org/?topic=83743) project.


Title: Re: Please test (if you dare): next-test 20120519
Post by: Diapolo on June 10, 2012, 12:41:20 PM
Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process :D.

Dia


Title: Re: Please test (if you dare): next-test 20120519
Post by: phelix on June 15, 2012, 07:48:13 PM
Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process :D.

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)


Title: Re: Please test (if you dare): next-test 20120519
Post by: Red Emerald on June 15, 2012, 09:13:55 PM
Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process :D.

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)
Cant you just "git clone git@github.com:luke-jr/bitcoin -b next-test" and always have the latest? That's what I do.


Title: Re: Please test (if you dare): next-test 20120519
Post by: Diapolo on June 15, 2012, 09:19:32 PM
Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process :D.

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)
Cant you just "git clone git@github.com:luke-jr/bitcoin -b next-test" and always have the latest? That's what I do.

As luke-jr uses cross-compilation or perhaps the official release-process via Gitian for this, it will show if my patches break something I can't detect, because I'm compiling own builds on Windows.

Dia


Title: Re: Please test (if you dare): next-test 20120519
Post by: Luke-Jr on June 22, 2012, 05:54:56 PM
Superceded with next-test 2012-06-21 (https://bitcointalk.org/?topic=89099)