[15:17:32] *** Joins: aguycalled (~user@unaffiliated/aguycalled) [15:17:37] *** Server sets mode: +cnt [15:17:38] *** Quits: aguycalled_ (~user@unaffiliated/aguycalled) (Ping timeout: 260 seconds) [15:57:29] It's collapsed [15:57:36] You need to expand it [15:58:42] https://cdn.discordapp.com/attachments/416000318149754881/727885900482084924/Capture.PNG [15:58:56] You need to expand the section that you wanna look at [15:59:23] My gitian build just finished [15:59:36] Looks like the WINDOWS_BITS issue is now fixed: b1dd88cdd8bf09af2539d0b345e647129d8fd55c92b6d824b6ecc53efd531028 navcoin-5.0.1-win.tar.gz ca3032cab6a82629085ce2e04a799be001d384a1fd9b1e7ab6bf132a191a678e navcoin-5.0.1-win32-debug.zip e3d3aa742752ada8b51d8e3c7012c9cc2f0782d567d5fc376d95df65f837a1aa navcoin-5.0.1-win32-setup-unsigned.exe 4567a0cf593ef67b6633c051eea7700bba4c9fdf1cd1f1f9f72f0cbdde2ccace navcoin-5.0.1-win32.zip [15:59:36] 04fb9d832b4bd513df57008513272ac097b5b886c0b07facb795a66868d7975c navcoin-5.0.1-win64-debug.zip 6766f257e886ae1fc92bb2e84cfa483604b0356d74ebed502e5c4c3d7663304a navcoin-5.0.1-win64-setup-unsigned.exe b0e72c4d327aa28cef8b45f77b3591e9fc5e96f22605c551f3c5d3b93e0a0573 navcoin-5.0.1-win64.zip da7d9e8ca0bad740e61157eb04e09346c26033084285264d6c5bc76bc7eb880e src/navcoin-5.0.1.tar.gz 5485bedfe181f03f5e7695cb7a733435706b5a7c37d8b675ccbd065cce7fe2dd [15:59:37] navcoin-osx-5.0.1-res.yml [16:03:13] I've tried to replicate it locally, by running the build like this: cd depends make -j12 HOST=i686-pc-linux-gnu NO_QT=1 cd .. ./autogen.sh ./configure --prefix=`pwd`/depends/i686-pc-linux-gnu --enable-zmq --enable-glibc-back-compat --enable-reduce-exports LDFLAGS=-static-libstdc++ --disable-bench --disable-dependency-tracking make -j24 test/pull-tester/rpc-tests.py -parallel=3 --coverage --failfast [16:03:19] But it passes for me locally [16:03:24] So not sure what is causing the timeout [16:14:58] @aguycalled I only tested this on devnet: https://github.com/navcoin/navcoin-core/pull/724 [16:15:02] But seems good [16:15:16] I did not have a mainnet node with index handy [16:15:47] maybe @sakdeniz or @prodpeak can confirm it works correctly [16:16:16] Actually yeah, they are gonna be using this alot, would make sense to get them to review 😄 [16:16:17] tested on mainnet [16:16:25] works without problem [16:16:28] Nice [16:16:37] Can you add a review to the PR? [16:16:41] I think we can merge this [16:16:43] sure [16:16:51] PR 724 [16:17:14] @aguycalled here is the test suite running the 32bit build for me locally: ................................ multi_rpc.py: Initializing test directory /tmp/test6vj9fpme/56 Stopping nodes Cleaning up Tests successful Pass: True, Duration: 17 s ............. httpbasics.py: Initializing test directory /tmp/testzmo2c9m0/57 Stopping nodes Cleaning up Tests successful Pass: True, Duration: 32 s ............................. [16:17:15] getchaintips.py: Initializing test directory /tmp/testb95grs6v/61 Stopping nodes Cleaning up Tests successful Pass: True, Duration: 147 s .................................................................... merkle_blocks.py: Initializing test directory /tmp/testymtra64_/54 Mining blocks... Stopping nodes Cleaning up Tests successful Pass: True, Duration: 52 s .............. zapwallettxes.py: Initializing test directory [16:17:15] /tmp/testimye16uu/55 Mining blocks... Stopping nodes Cleaning up Tests successful Pass: True, Duration: 67 s ............................................... nodehandling.py: Initializing test directory /tmp/testz61abock/53 Stopping nodes Cleaning up Tests successful Pass: True, Duration: 69 s [16:17:17] Working fine [16:17:28] I'm kinda confused what the cause for it to hang on travis is [16:17:45] I'm building it exactly the same way as travis and running the exact same tests as well [16:18:35] i am not in reviewers list [16:18:46] a comment is enought? [16:19:27] Go here: https://github.com/navcoin/navcoin-core/pull/724/files [16:19:36] Top right, you should be able to do a review [16:21:20] done [16:23:42] @aguycalled I'm away from my computer but testnet got stuck on the addressindex branch [16:23:53] I'll confirm the error for you this evening and attempt a reindex [18:37:12] <0x2830> I'm reading your changes @mxaddict TY