remove qvm-ng #300
remove qvm-ng #300
Conversation
|
I'm also sorry to see it go, but it is what it is. Do the tests still pass locally? The runner is still mad about some package renaming in CL-QUIL. |
|
No they don't. Some JSON library API-induced bit rot. It's probably fixable tho without too much work. If you or someone else uses it, I can fix the tests and keep it going. |
|
Oh I meant the tests on the rest of QVM, after the NG deletion is applied — the thing the GitHub test runner is trying & failing to do. |
|
Oh yes, they should be, but I'll have to double check. We need to change test runners desperately so that they're meaningful. :S |
There was a problem hiding this comment.
qvm-ngn't amiright?
R.I.P. CrustyOldDocketFile gone but not forgotten
|
👋🏽 😿 |
|
never forget QVMaaS. |
|
pqvm ftw |
d(-_-)bvm |
p(-_-)qvm persistent-but-only-in-our-hearts-qvm Maybe the real treasure was the PERSISTENT-QVMs we made along the way... |
Sorry to see it go, but it has not been developed, and it is not used in production.
Fixes #299 #296