Pages:
Author

Topic: The bug could be found!!! run them both in same test envrionment - page 4. (Read 4013 times)

legendary
Activity: 1246
Merit: 1077
This is not accurate.

There was, indeed, testing on the testnet with a full (1 MB) block. This was accepted by both the 0.7 and 0.8 versions. There is no concern here.

Slush's block should have produced the same valid block. However, the block was structured carefully as to expose a problem in 0.7 that was never discovered. Not only was this an extremely difficult problem to catch, but its finding would in fact not have been accelerated with a mixed testnet. The introduction of 0.8 into the equation would actually delay finding the bug, as it would mean less time spent testing edge cases on 0.7.
donator
Activity: 1218
Merit: 1079
Gerald Davis
You of course tested both v0.7 and 0.8 on testnet found the flaw and reported it to the development team.  When they ignored you, you went viral sharing the incompatibility with everyone you knew.  Thanks goodness we had you ... er wait you didn't do any testing.  Most of the developers are unpaid volunteers.  Given your extensive testing experience why aren't YOU doing something?
legendary
Activity: 2632
Merit: 1023
The Bug Could be found if testing was done by having both 0.7.0, and 0.8.0 tested together in the test environment under suitable conditions, and watching the outputs with various bug catches, eg BlockFill.percent()


There should be a standardized set of test tools that extract information about critical parameters.

It is unchallenged that not all people will upgrade uniformally so why the 0.8.0 is not being tested with prior versions is a false argument, doomed to throw a bug out, and this has now been proven QED

I am somewhat disappointed 0.7.0 was not the test environs ( I assumed you were doing that) and more disappointed that currently a good percentage of "talented people" are claiming that this bug could not have been detected

It seems dev is concentraing on single points like upgrade this upgrade that, but not viewing BTC as the full system as it is
(and I suggest the full system maybe Crypto/BTC is about re-aragning human activity/social fabric...and that why is that to be very distibuted....not on a few asic miners and not through an exchange that can calim 80% of all bitcoin, though the latter is not such a problem)

When I write a collision engine for example I ratchet up/down various parameters to the absurd to see what will happen, and I use various checks to test faults, eg use conservation of momentum forums versus velocity/position/mass / momentum eqns


similar weighted methods could be used in almost any test environment

What you are doing by not doing this is BTC will tend to be the best possible test bed for something like LTC or maybe TRC latter using a closer system to BTC than LTC, or other Coin, as LTC/TRC will now not make this mistake!!!, but BTC stress-tested everything for them.

LTC/TRC are going to at least arbitrage in from BTC the security they gain BTC mistakes and from not being first


TL:DR
BTC is turning into a possible test system for LTC/TRC etc
Pages:
Jump to: