| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | ci: Run tests with DEBUG=1 too | Miquel Sabaté Solà | 2024-12-02 | 1 | -0/+3 |
| | | | | | | | | | Since 32e880127366 ("Prepend the name of the task on debug") we are executing some code when DEBUG is present. Hence, the building might be different in this scenario too. Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com> | ||||
| * | Add files for contributing to the project | Miquel Sabaté Solà | 2024-11-25 | 2 | -0/+30 |
| | | | | | Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com> | ||||
| * | tests: Only test initrd addresses on debug | Miquel Sabaté Solà | 2024-11-25 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | In initrd tests, and in general, we only need to check that the function did something. As in, that it set the entry addresses somewhere and did not leave them NULL. This is going to be performed from now on on CI and regular tests. And, just if you want to go the extra mile, we will run specific tests that check on memory addresses but that are not guaranteed to work. This is to be replaced in the future by having some proper debugging output. As in, having a message at kernel boot time specifying the addresses being used among other info. This needs a more complex printk utility, of course. Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com> | ||||
| * | Add CI job | Miquel Sabaté Solà | 2024-09-24 | 1 | -0/+29 |
| This will ensure that the code style is preserved and that commits being pushed at least build successfully. Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com> | |||||
