394
edits
Changes
no edit summary
In CRIU it is used to grab patch series from the CRIU mailing list, create a new git branch which is tested by Travis, and report success/failure back to the mailing list.
In CRIU it is used to grab patch series from the CRIU mailing list, create a new git branch which is tested by Travis, and report success/failure back to the mailing list.
'''For more info, see [[Patchwork]]'''.
=== Non-x86 architectures ===
=== Non-x86 architectures ===
The process consists of "git clone" the kernel, compiling it, and using kexec to reboot to a new kernel. The catch is we have to use CRIU itself to checkpoint/restore the travis control process, so that the VM is not lost to Travis upon reboot. Please see [https://avagin.github.io/travis-kexec-criu this article] for more details on the process.
The process consists of "git clone" the kernel, compiling it, and using kexec to reboot to a new kernel. The catch is we have to use CRIU itself to checkpoint/restore the travis control process, so that the VM is not lost to Travis upon reboot. Please see [https://avagin.github.io/travis-kexec-criu this article] for more details on the process.
To check the recent builds, see https://travis-ci.org/avagin/criu/branches (look for <code>linux-next-daily</code> branch).
To check the recent builds, see https://travis-ci.org/avagin/linux/builds .
=== Enable Travis CI for your repo ===
=== Enable Travis CI for your repo ===
* [[ZDTM test suite]]
* [[ZDTM test suite]]
* [[Linux-next]]
* [[Linux-next]]
* [[Patchwork]]
== External links ==
== External links ==