wwilson

7 ms·

61.
by wwilson 2y ago
The simulation is a completely generic Linux system, so we can run anything (including NodeJS). If your build tool can produce Docker containers, then it will work with us. We don't run this on your production server, but in the same s
62.
Debugging in the Multiverse(antithesis.com)
201 points by wwilson 2y ago|58 comments
63.
No Ghost Policy(antithesis.com)
1 points by wwilson 2y ago|1 comments
64.
Security at Antithesis: A Manifesto(antithesis.com)
1 points by wwilson 2y ago|0 comments
65.
by wwilson 2y ago
Good suggestion on leaving LD_PRELOAD unset if it was previously unset. We will fix that. I’m torn on whether MD_PRELOAD or LD_PRELOAF is more obnoxious to other programs. Fun fact: A previous version of this program used an even more inscr
66.
by wwilson 2y ago
Great point! I'll update the post to mention that.
67.
by wwilson 2y ago
Biggest advantages I know of for dynamic linking: * You can use the LD_PRELOAD trick to override behavior at runtime. * You can run with entirely different implementations of the dynamically linked library in different places. * Software ca
68.
by wwilson 2y ago
Our artist is on vacation, and some fool gave the CEO access to Midjourney.
69.
by wwilson 2y ago
Post author here. Feel free to ask me any questions about the piece of software that I most regret having had to write.
70.
At the Mountains of Madness(antithesis.com)
153 points by wwilson 2y ago|85 comments
71.
by wwilson 2y ago
I'm obviously biased, but if I imagine a world where I had nothing to do with Antithesis, I actually do think an autonomous system playing and beating Zelda is the kind of thing I would enjoy reading about on HN.
72.
Solving Zelda with the Antithesis SDK(antithesis.com)
36 points by wwilson 2y ago|8 comments
73.
by wwilson 2y ago
Our projects have some features in common, but are pretty much unrelated. Hermit is a deterministic userland, whereas we enforce reproducibility at the hypervisor level and with the right device drivers can support any OS. The most interest
74.
by wwilson 2y ago
Thank you. Comments like this are why I love HN.
75.
by wwilson 2y ago
Hmm... looks like Vimeo is currently having some kind of outage. If anybody at Vimeo is reading this and wants some help with testing backend systems, email is in bio.
76.
by wwilson 2y ago
We find a ton of glitches in Mario, and even more in other games. See, e.g.: https://vimeo.com/807601164
77.
by wwilson 2y ago
It is absolutely possible to write a large stateful system from the ground up so that autonomous testing techniques can be applied to it. FoundationDB and Tiger Beetle are both examples of this, I think Resonate might be another one, and To
78.
by wwilson 2y ago
It's possible you did not make it to the end of the talk where I explain this, but the thing that excites me is that we can now apply fuzzing and related techniques to things which are neither Nintendo games nor tiny stateless librarie
79.
by wwilson 2y ago
We are huge fans of tom7 and that paper was one of our inspirations for using NES as a domain for researching autonomous state space search! I think he does a very good job of explaining why the problem is hard.
80.
by wwilson 2y ago
This is actually an incredibly deep and difficult question to answer. I would expect no less from cperciva. :-) As I mention in the talk, you get very bad tactical performance from taking a uniform random distribution and piping it into the
81.
by wwilson 2y ago
Thanks for flagging this! The work we're announcing today was completed in 2018, and we have since moved on to much more challenging problems both in the Nintendo domain and elsewhere. Totally not looking to pick a fight over priority
82.
by wwilson 2y ago
There was a LOT of discussion of this in the Q&A after the talk. Currently we have 4 main approaches: (1) There's some stuff that's pretty much a bug for every program. If it segfaults, exits with a nonzero code, OOMs, trigger
83.
by wwilson 2y ago
This is Will (I gave the talk linked in the post). Happy to answer any questions about this work, or how it generalizes to testing things that aren't Nintendo games.
84.
How Antithesis finds bugs(antithesis.com)
160 points by wwilson 2y ago|53 comments
85.
by wwilson 3y ago
If you would like us to repro this bug in Antithesis and help you debug it there, email me and I’ll hook you up: will@antithesis.com
86.
Antithesis announces Artificial General 8-bit Intelligence (AG8I)(antithesis.com)
21 points by wwilson 3y ago|0 comments
87.
by wwilson 3y ago
This bug definitely didn’t involve SDK integration, because our SDK didn’t exist yet when we found it! I believe CockroachDB was running our instrumentor over their binaries though. So call it an in-between level of integration.
88.
by wwilson 3y ago
A drawback of our approach is absolutely that it is expensive to test extremely large volumes of data or compute this way. Even before you start running into physical limitations of our current platform, you will probably be complaining abo
89.
by wwilson 3y ago
That's true. And it's also true that investing heavily would take time, and the more time goes on the less likely we are to be acquired or disappear (or for the acquisition to be by somebody who wants to resell this as I note abov
90.
by wwilson 3y ago
Your understanding of our approach is pretty much correct. As for interesting coverage metrics... stay tuned! We're going to write about this a lot in the future!

More ›