Closed ydahhrk closed 8 years ago
Ok so I think this is how it looks like right now. 0b55c253c7b19b14b99e0c2d4c525f2cc05add84
It's not perfect, but at least it tries (as in it should be able to) to compile and test Jool against all the Linux kernels currently installed in the host machine. Unfortunately kernels must be manually installed as I couldn't get the kernels found in Linux's Git to work in my machine (I was planning to automate the compilation and installation of those kernels as well).
Last, but quite definitely not least...
The ITESM guys left, so nobody is testing Jool works in wild environments and stray kernels. This led to a very embarrassing day one panic and the compatibility section not actually saying much.
So that sucks. It didn't have much priority because it had been really long since the last time that yielded a bug report, and the deployment of a permanent test network that had access to constant natural traffic seemed far more productive. But whatever; those tests need to come back. And they need a refactor because they're a serious pain to run.
The rest of the test suite has proven to be effective, but it could still use some maintenance. The white box tests need documentation (in case users want to run them) and a refactor (in newer kernels, the makefile needs tweaking because Kbuild no longer allows several modules to be compiled in the same folder). The gray box tests need to be published; all that's visible is strange-looking code and no actual tests. The black box test (the network) is fine, I think.
These might also help enhance the suite.