Invalidating postdata

Posted by / 12-Oct-2019 21:49

Invalidating postdata

Create identical pre- and post-program self-assessments exclusively for mentees.

For confidentiality, individuals will be assigned a unique numerical identifier.

Cannot Send Request :~/node/bitcoin$ ./qa/pull-tester/pruning Running 2nd level testscript ..When designing a mentoring program, first determine your program goals.These will form the basis for evaluating whether the program has met its expected objectives.Cannot Send Request $ git log --oneline -1 b6d5e32 Make fee aware of min relay in RPC test $ qa/pull-tester/pruning --tmpdir=/var/tmp/BTC Running 2nd level testscript .. This test requires 4GB of disk space and takes over 30 mins (up to 2 hours) Mining a big blockchain of 995 blocks Check that we haven't started pruning yet because we're below Prune After Height Success Though we're already using more than 550MB, current usage: 590 Mining 25 more blocks should cause the first block file to be pruned Success Usage should be below target: 479 Check that we'll exceed disk space target if we have a very high stale block rate Mine 24 (stale) blocks on Node 1, followed by 25 (main chain) block reorg from Node 0, for 12 rounds Usage can be over target because of high stale rate: 638 Check that we can survive a 288 block reorg still Current block height: 1320 Invalidating block at height: 1033 423699603f0fe282968c6b7705e431aa44a655e2a511854d6cf1750d5505430a New best height 1032 Generating new longer chain of 300 more blocks Reconnect nodes Verify height on node 2: 1332 Usage possibly still high bc of stale blocks in block files: 638 Mine 220 more blocks so we have requisite history (some blocks will be big and cause pruning of previous chain) Usage should be below target: 447 Test that we can rerequest a block we previously pruned if needed for a reorg Will need to redownload block 1033 Rewind node 0 to prev main chain to mine longer chain to trigger redownload.Blocks needed: 233 Verify node 2 reorged back to the main chain, some blocks of which it had to redownload Done Stopping nodes Cleaning up Tests successful $ git log --oneline -1 b6d5e32 Make fee aware of min relay in RPC test $ qa/pull-tester/pruning --tmpdir=/var/tmp/BTC Running 2nd level testscript .. This test requires 4GB of disk space and takes over 30 mins (up to 2 hours) Mining a big blockchain of 995 blocks Check that we haven't started pruning yet because we're below Prune After Height Success Though we're already using more than 550MB, current usage: 590 Mining 25 more blocks should cause the first block file to be pruned Success Usage should be below target: 479 Check that we'll exceed disk space target if we have a very high stale block rate Mine 24 (stale) blocks on Node 1, followed by 25 (main chain) block reorg from Node 0, for 12 rounds Usage can be over target because of high stale rate: 638 Check that we can survive a 288 block reorg still Current block height: 1320 Invalidating block at height: 1033 423699603f0fe282968c6b7705e431aa44a655e2a511854d6cf1750d5505430a New best height 1032 Generating new longer chain of 300 more blocks Reconnect nodes Verify height on node 2: 1332 Usage possibly still high bc of stale blocks in block files: 638 Mine 220 more blocks so we have requisite history (some blocks will be big and cause pruning of previous chain) Usage should be below target: 447 Test that we can rerequest a block we previously pruned if needed for a reorg Will need to redownload block 1033 Rewind node 0 to prev main chain to mine longer chain to trigger redownload.

invalidating postdata-51invalidating postdata-41invalidating postdata-2

:~/node/bitcoin$ ./qa/pull-tester/pruning Running 2nd level testscript ..

One thought on “invalidating postdata”