Matches for test, 2087 total results Sorted by newest | relevance
Wed Feb 24 21:01:13 UTC 2016 <phf> l1 or l2 runs trb, where behavior can be improved. better sync mechanisms, bandwidth/cpu conservative network activity, etc. anyone in the wot can also be punished for abuse, i.e. if asciilifeform starts sending me gigs of bogus transactions, and it's not a test and he can't be reasoned with, etc.
Wed Feb 24 04:21:28 UTC 2016 <mod6> i'll test that out tomorrow when i get a sec.
Wed Feb 24 01:25:10 UTC 2016 <asciilifeform> will test.
Sun Feb 21 16:37:27 UTC 2016 <asciilifeform> but i can't promise this, and can't be bothered to test, for reasons already described.
Sun Feb 21 01:42:03 UTC 2016 <asciilifeform> mircea_popescu: say we do things precisely as you described. and tomorrow i publish a patch. now everyone who wants to test it, cannot apply it at all unless he is willing to use my tree wholesale. instead he has to MANUALLY merge it in, line by line. and then i end up back-and-forth-ing over his typos for the next month, instead of doing ANYTHING else
Sat Feb 20 21:45:13 UTC 2016 <mod6> until we finally get a test branch and so on and so forth, this stuff has to be ~perfect~ or we've got zip
Sat Feb 20 21:44:58 UTC 2016 <ben_vulpes> mircea_popescu: only if "actual test cycles" only means "#b-a test cycles"
Sat Feb 20 21:44:09 UTC 2016 <mircea_popescu> ben_vulpes really ? i thought it was pretty fast for an actual test cycle ?
Sat Feb 20 19:31:37 UTC 2016 <jurov> mod6 looks like it's fixed, my test email went through.... check whether your email was queued
Fri Feb 19 20:50:32 UTC 2016 <mod6> TMSR Testers: Last chance to test beta4!
Fri Feb 19 17:19:22 UTC 2016 <asciilifeform> another example: official 'tempest' test specs.
Tue Feb 16 23:17:37 UTC 2016 <pete_dushenski> i'd consider those letters i wrote to peck and lee as 'dry test runs' but mebbe not enough forced meme!
Tue Feb 16 23:16:05 UTC 2016 <BingoBoingo> Maybe start some dry test runs? Force a meme or something?
Tue Feb 16 21:49:35 UTC 2016 <ben_vulpes> asciilifeform: http://thebitcoin.foundation/test-builds/v0.5.4/amd64/bitcoin-v0_5_4-TEST2.tar.gz << unzip, ./build_bitcoin.sh, make tea
Sun Feb 14 23:42:33 UTC 2016 <asciilifeform> it is only 'to yourself' if your test is successful !
Sun Feb 14 23:41:50 UTC 2016 <asciilifeform> so how to test?.
Sun Feb 14 21:44:14 UTC 2016 <mod6> i'll give it a few days and then will roll up a full bundle. i've got an automated test for this case now too.
Sun Feb 14 19:08:13 UTC 2016 <mod6> ok, so instead what I'll do here is add an automated test to check for this, so i don't regress later. and then most likely will put out a 3rd beta patch for people to test/review.
Sun Feb 14 18:04:57 UTC 2016 <mod6> to test it, i had to hand-diddle one of the vpatches. easy enough to do. if someone is doing something very strange or bad or whatever on their system it could lead to an infinate loop.
Sun Feb 14 15:38:32 UTC 2016 <mircea_popescu> asciilifeform for the sake of argument, consider this issue : <asciilifeform> but the hamilton thing is garbage. ; hamiltoninc : "Here are some properties and features that make 001 unique: Always number one when put to the test."