Anyone know about work along the lines of HAL? Dave, I hate to interrupt, but I’ve detected a fault in one of my circuits. I’ve stumbled on a need for this as well as a way to implement it: Software that re-runs its test suite on itself after updating its fixtures based on new environmental fact…

Correct me if I’m interpreting this incorrectly, but isn’t what you’re describing like a CI pipeline that runs when certain conditions are met rather than on code commit? I’m interested since I working on an app that tests test quality and this might be in the same wheelhouse.

I know some embedded engineers write code that checks memory content at runtime to ensure the code being executed is actually what is supposed to be executed. Something to do unstable hardware. And of course fixing that after detecting mismatch.

Actually, it’s a piece of an ETL pipeline that will run daily. And so I’d it to refuse to run if the input format has changed too much. It’s Haskell that I’m going to try implementing in Elixir: GitHub - public-law/nevada-revised-statutes-parser: Parses the Nevada NRS into well formed JSON · GitHub …

Have you looked at mix test.watch ? A far cry from HAL but it allows you to have your tests re-ran as you are modifying your code.

Thanks! I’ve wanted an Elixir equivalent of Haskell’s stack test --file-watch

[image] dogweather: Dave, I hate to interrupt, but I’ve detected a fault in one of my circuits. You should probably view this in context. Any “true” AI – like a sentient, intelligent being – that is much better and more durable than us, will likely have a stream of consciousness. Part of that…

If you code for the “happy” path—and make your pattern matches really strict—you will see it in your error logs every time your application encounter something unexpected. You can then decide on what to do in these discovered cases. Besides the stuff that is build in to OTP (i.e. Supervision), patt…

Safe healing, I think it could if you meant to automatically get back in time instead of trying to invent a new patch to fix itself. Like, if a test fails or that some of the web pages display errors, you could code something using git bissect that would find the culprit and go back in time enough t…

It’s only more complicated because nobody coded that yet. But indeed it would merge some aspects of CI into the server itself. That’s probably not a very good idea except for a fun project (for some definition of fun).

Elixir Programming Language Forum

A self-testing application?

Questions & Help Questions

Zesky665 January 10, 2019, 10:09am 10

Isn’t this just a more complicated way to do CI?