From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyril Hrubis Date: Thu, 3 Sep 2020 11:24:48 +0200 Subject: [LTP] [RFC] ltp test add reboot function In-Reply-To: References: <20200824074226.GB2466@yuki.lan> <20200828130638.GD10501@yuki.lan> Message-ID: <20200903092448.GC6285@yuki.lan> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Hi! > >Also I do consider the whole concept of running the test exectution > >framework on the same machine as the testcases broken by desing for > >kernel related tests. The way forward is the patchset send by Richard > >that implements simple test executor that runs on the machine under test > >and communicates with a execution framework that runs on a central > >server. > > I agree with some of your views??? the test architecture server/slave is most > common test method. but I also want to know what kind of connection > method between test machine and central server, the ssh , adb or serial? > > because my test machine is a cellphone, our purpose is test the kernel before > androidOS , so I build debianOS on our haraware, and we can only used the > serial port communicate with our testmachine. As for LTP the tool Richard is working on is a daemon that runs on the SUT[1], will be quite possibly started during the boot and will listen on pre-defined transport channels, e.g. TCP, serial, bluetooth, etc. The protocol itself should be transport agnostic and should work over anything that can transport bytes. But that is something that is under development at the moment. -- Cyril Hrubis chrubis@suse.cz