Quoting Subrata Modak ([EMAIL PROTECTED]): > Hi, > > Recent OLS 2008 was a critical point in LTP´s evolution, as i got the > opportunity to meet several people across the Linux ecosystem, and > listened to their opinion about LTP. Here i would start a mail chain > with the above Subject line, discuss each and every issue in this > mailing list, collate everybody´s opinion on those issue(s) and take > action accordingly. These are the people i encountered: > > 1) People, who uses LTP heavily. And they suggested lots of improvement > to it. We will discuss those issues in mails from now, > > 2) People, who have heard about LTP and not used it till now. They > promised that they will give a try, > > 3) People, who has never heard about it. So, it was an opportunity to > convey them what LTP is all about. I hope people in Category 2 & 3 will > start using LTP soon, and we will get an enlarged user base and hence > bringing more contribution in future. > > ================= > ISSUE # 1 > ================= > The heavy users made a point of LTP having the capability to automate > testing completely. What they meant was LTP to have capability to do: > 1) Kernel Build, > 2) Kernel Install/Distro install, > 3) Then do specific/all tests, > > They said that this feature will simplify the way they work. I would > like to know what you all think about this. > > What i feel is, every project should evolve and should be flexible
(my 2c) if every project evolves, then every program will end up being emacs+firefox+eclipse all in one. If people want what you describe above, then a new project should be created. It could actually be pretty spiffy, and quite simple. It could grab distro images to autoinstall a kvm image, install some software and/or patches that I specify, grab a kernel I specify, build it, grab the most recent ltp release and compile/install it, run the tests, and give me the results. I know there are suites out there that do that type of things on physical grids now. A smaller version of that which just creates a kvm partition on my own machine would be like a personal version of one of those. Ideally it would be accompanied by an online store of very targeted distro install .isos that auto-install themselves if I just do kvm -hda newimage.img -cdrom distro.iso -boot d. And through judicious saving of installed images and use of -snapshot, this project could lead to truly repeatable ltp results. "Use this kernel with this config on this qemu-img, and you'll see that chown is failing." Cool. But putting this in ltp seems wrong to me. Let's keep ltp's focus on testing. So really the hardest part of starting something like this might be the creation of some auto-install distro images. > enough to meet their users requirement dynamically, and should not be > tied down with the limitations of it´s initial design constraints. If > automating kernel build, install and tests is a requirement coming from > the user community, then we need to give a hard look at it. I would like > to know what you think about this. > > Regards-- > Subrata > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
