11–20 of 56 posts
> Back then Spanner wasn’t public yet and a lot of people misinterpreted the CAP theorem to say that a strongly consistent database couldn’t also be highly available in the face of network faults.
This is for a distributed database product that claims to bypass the CAP theorem or have I misunderstood? > Back then Spanner wasn’t public yet and a lot of people misinterpreted the CAP theorem to say that a strongly consistent database couldn’t also be highly available in the face of network faults. - https://antithesis.com/blog/is_something_bugging_you/
This is for a distributed database product that claims to bypass the CAP theorem or have I misunderstood? > Back then Spanner wasn’t public yet and a lot of people misinterpreted the CAP theorem to say that a strongly consistent database couldn’t also be highly available in the face of network faults. - https://antithesis.com/blog/is_something_bugging_you/
This is for a distributed database product that claims to bypass the CAP theorem or have I misunderstood? > Back then Spanner wasn’t public yet and a lot of people misinterpreted the CAP theorem to say that a strongly consistent database couldn’t also be highly available in the face of network faults. - https://antithesis.com/blog/is_something_bugging_you/
A lot of us worked at FoundationDB, but this is a new company (Antithesis) which develops autonomous testing and debugging tools.
Earlier quoted context omitted.
A lot of us worked at FoundationDB, but this is a new company (Antithesis) which develops autonomous testing and debugging tools.
By the way, that's one cool-looking cybernetic ant-eater. Is that what an ant-ithesis supposed to look like?
Or what if my bug is caused by bitflips in failing memory, that lead to impossible control flow paths being hit? Think something like:
if x != 0:
return 1/x
Not hypothetical scenarios, both real bugs I've had to troubleshoot in my career.
We do something similar in house where I work. Is it hard to onboard new customers? Since they make a special container for you they basically adopt your build system, which may be hard for them. Does this go beyond mutation testing?
With most of our customers, they don't actually have to change their build system at all. We take their normal CI products, plus a small amount of special configuration, and run them. This is actually a good thing because we're testing something very similar to what runs in production. The kinds of state space exploration we do are a lot more general than mutation testing. Our current product does exploration by (1)…
How does this deal with non-determinism from the outside world? For example, let's say one of my tests is flaky because it asks an external service to give it some data, and that external service is flaky in what it returns? Or what if my bug is caused by bitflips in failing memory, that lead to impossible control flow paths being hit? Think something like: if x != 0: return 1/x Failing with an error because x is 0.…
https://antithesis.com/docs/applications/reliability/fault_i...
If you know somebody who will pay money for us to prioritize this feature, let me know! Otherwise, I'm sure we'll get to it eventually. We have all kinds of crazy ideas for new faults.
Communication with the outside world is something that we obviously have to ban. This means that all of the inputs to your system are being provided by our platform, and that any dependencies have to be mocked, or run inside the hypervisor with you.
In practice this can cause friction for people with a ton of dependencies. Some of the most common things we've already mocked (for example we have an entire fake AWS that we can run in there with you), and if your dependency is one of our existing customers, we can probably work something out...
Earlier quoted context omitted.
With most of our customers, they don't actually have to change their build system at all. We take their normal CI products, plus a small amount of special configuration, and run them. This is actually a good thing because we're testing something very similar to what runs in production. The kinds of state space exploration we do are a lot more general than mutation testing. Our current product does exploration by (1)…
Thanks! Where does the "want" come from to compare your "got"s to? If the customer code handles errors gracefully, can you still surface undesirable behavior?