You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intention is that all cleanups and refactoring should happen over there. Please discuss everything needed for this to happen over there. Feel free to open issues as needed. Anyone who wants commit access, please see: LuaJIT/LuaJIT-test-cleanup#1
When everything is done, it should be merged into this repo 'flat', without the history. The cleanup history will be quite messy and not very useful here. [TBD whether this is to be merged or split off, too.]
The text was updated successfully, but these errors were encountered:
I'm currently the maintainer of LuaJIT in Fedora. I added the LuaJIT-test-cleanup repo to our package and with minimal changes the tests are passing.
I see that there are several pull requests in the repo, but they all just bitrot. Is there still a plan to integrate the tests or remove them entirely?
I do not think distros should be doing the testing. Various people are already running permanent CI tests and fuzzers. And with special debug/assert builds, which have a much higher likelihood than production builds to turn up anything.
When, if and how the tests are merged or split is yet to be determined.
Oh, it is part of the packaging process to run tests. You really want that as a distribution:
a) We often build on more platforms than developers do (x86, arm, ppc, s390, ...)
b) You want to know in a distro if an update of a package breaks another package.
c) Untested code is broken code ;-)
I've just added: https://github.com/LuaJIT/LuaJIT-test-cleanup
The intention is that all cleanups and refactoring should happen over there. Please discuss everything needed for this to happen over there. Feel free to open issues as needed. Anyone who wants commit access, please see: LuaJIT/LuaJIT-test-cleanup#1
When everything is done, it should be merged into this repo 'flat', without the history. The cleanup history will be quite messy and not very useful here. [TBD whether this is to be merged or split off, too.]
The text was updated successfully, but these errors were encountered: