Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2009:dverkamp:journal:week1 [2009/05/26 12:05] drv monday + tuesday (partial) |
soc:2009:dverkamp:journal:week1 [2009/06/01 17:44] (current) drv |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Journal Week 1 ===== | ===== Journal Week 1 ===== | ||
| - | ==== Monday ==== | + | ==== Monday, May 25 ==== |
| Wrote up a list of some potential test cases on [[soc:2009:dverkamp:notes:start|notes]] page. | Wrote up a list of some potential test cases on [[soc:2009:dverkamp:notes:start|notes]] page. | ||
| - | ==== Tuesday ==== | + | ==== Tuesday, May 26 ==== |
| Discussed Autotest framework with mcb30; goals for the week: | Discussed Autotest framework with mcb30; goals for the week: | ||
| Line 16: | Line 16: | ||
| Also mcb30 discovered the reason for the apparent increase in size with GCC 4.4.0 (unneeded .eh_frame sections were being counted in 'size' output); with a patch to eliminate these sections, GCC 4.4.0 now has the smallest total code size of all the GCC versions I'm testing ([[http://drv.nu/gpxe/size/]]). | Also mcb30 discovered the reason for the apparent increase in size with GCC 4.4.0 (unneeded .eh_frame sections were being counted in 'size' output); with a patch to eliminate these sections, GCC 4.4.0 now has the smallest total code size of all the GCC versions I'm testing ([[http://drv.nu/gpxe/size/]]). | ||
| + | |||
| + | ==== Wednesday, May 27 ==== | ||
| + | |||
| + | Investigating Autotest architecture today. | ||
| + | |||
| + | Some notes: | ||
| + | |||
| + | * The Autotest client is in the "client" directory of the full download; this seems to be usable without any of the other pieces, at least for testing. | ||
| + | * Within client, there are several sample "control files"; for my initial goal (building gPXE), samples/build is the most interesting. | ||
| + | * The control files use "job" objects; the build sample uses job.kernel, which seems to be located in bin/kernel.py. | ||
| + | * bin/kernel.py has several methods involved in building a kernel, like "kernelexpand" (download, extract, patch kernel), "config" (use a specific config or defconfig), and "build" | ||
| + | |||
| + | ==== Thursday, May 28 ==== | ||
| + | |||
| + | Some investigation of cloning Autotest SVN repository with git (see http://git.drv.nu/?p=autotest.git). | ||
| + | |||
| + | ==== Friday, May 29 ==== | ||
| + | |||
| + | Spent most of the day reading BuildBot documentation (http://djmitche.github.com/buildbot/docs/0.7.10/) - I think this might be a better fit than Autotest. Autotest is closely tied to testing the Linux kernel (although there is at least one other project, KVM, that is not using it to test Linux kernels, although the KVM build process is not under its version of Autotest's control). BuildBot, on the other hand, is designed to coordinate building and testing of arbitrary projects, and it is in use by several large projects (http://buildbot.net/trac/wiki/SuccessStories). | ||
