|
Here is a list of things to do to merge the Toshiba and Sony code bases:
|
Here is a list of things to do to merge the Toshiba and Sony code bases:
|
|
|
== to do == * ftc run-test * store the fuego data, even if there is no matching jenkins job * store run.json file * e.g. I run ftc run-test bbb-poky-sdk Functional.hello_world testplan_quick * but there is no: /var/lib/jenkins/jobs/docker.testplan_quick.Functional.hello_world directory * create alternative fuego directory for "console" output and build status * time is wrong (47 years ago) * description is off * should be link to log * I faked DISTRIB * I faked post_script (the script from the xml file)
|
- ftc tasks: * add fuego-create-jobs to ftc (ftc create-jobs) * add fuego-delete-jobs to ftc (ftc delete-jobs) * add fuego-create-node to ftc (ftc create-node) * add fuego-delete-node to ftc (ftc delete-node) * allow ftc to run both inside and outside the container * have a different config inside the container from outside the container * detect whether in the container or not * add global configuration to ftc * specify board directory * specify test directory * specify log directories * specify build directories * have ftc run-test save result, and perform post_test * have ftc run-test replace the main sequence in (. functional.sh, . benchmark.sh, and . stress.sh) * rename all base scripts to fuego_test.sh * make board file writable for device dictionary entries * or, change ftc to put entries in another file and source that in board * fuego-rw/boards/bbb-poky-sdk.data * source /fuego-rw/boards/bbb-poky-sdk.data * or have overlay generator add it
|
* ftc tasks: * add fuego-create-jobs to ftc (ftc create-jobs) * add fuego-delete-jobs to ftc (ftc delete-jobs) * add fuego-create-node to ftc (ftc create-node) * add fuego-delete-node to ftc (ftc delete-node) * allow ftc to run both inside and outside the container * have a different config inside the container from outside the container * detect whether in the container or not * add global configuration to ftc * specify board directory * specify test directory * specify log directories * specify build directories * have ftc run-test save result, and perform post_test * have ftc run-test replace the main sequence in (. functional.sh, . benchmark.sh, and . stress.sh) * rename all base scripts to fuego_test.sh * make board file writable for device dictionary entries * or, change ftc to put entries in another file and source that in board * fuego-rw/boards/bbb-poky-sdk.data * source /fuego-rw/boards/bbb-poky-sdk.data * or have overlay generator add it
|
|
|
=== ovgen.py needs fixing === * trying to run job docker.Functional.fuego_board_check I get an error fromovgen (about Benchmark.bfoo not having a spec, or something){{{#!YellowBox++ run_python /fuego-core/engine/scripts/ovgen.py \ --classdir /fuego-core/engine/overlays/base \ --ovfiles /fuego-core/engine/overlays/distribs/nosyslogd.dist /fuego-ro/conf/boards/docker.board \ --testplan /fuego-core/engine/overlays/testplans/testplan_default.json \ --output /fuego-rw/work/docker_prolog.sh++ '[' '!' -z ']'++ python /fuego-core/engine/scripts/ovgen.py \ --classdir /fuego-core/engine/overlays/base \ --ovfiles /fuego-core/engine/overlays/distribs/nosyslogd.dist /fuego-ro/conf/boards/docker.board \ --testplan /fuego-core/engine/overlays/testplans/testplan_default.json \ --output /fuego-rw/work/docker_prolog.shTraceback (most recent call last): File "/fuego-core/engine/scripts/ovgen.py", line 611, in <module> run() File "/fuego-core/engine/scripts/ovgen.py", line 603, in run generateProlog(output, ofcls, classes, testPlans) File "/fuego-core/engine/scripts/ovgen.py", line 412, in generateProlog parseGenTestPlan(tpf, outfile, outFilePath) File "/fuego-core/engine/scripts/ovgen.py", line 497, in parseGenTestPlan raise SpecException("Cannot find test %s in spec list" % (testName))__main__.SpecException: u'Cannot find test Benchmark.bfoo in spec list'++ abort_job 'Error while prolog.sh file generation'++ set +x}}}
|
|
|
=== Functional.fuego_board_check * + create Functional.fuego_board_check * create job in jenkins * fuego-create-jobs --board bbb-poky-sdk -c Functional.fuego_board_check * failed due to missing testplan_default * add to testplan_default or * modify fuego-create-jobs to ignore that test is missing from testplan_default * + create job file manually (for now) * detect required fuego programs and target features * permissions to access /proc * permissions to home directory * shell features
|
- (1) figure out why deploy fails for Functional.fuego_board_check * use set -x
|
* (1) figure out why deploy fails for Functional.fuego_board_check * use set -x
|
|
|
== things that should work, when done == * ftc list-tests - OK * ftc list-targets - (stuff moved) OK * (done) change to use get_fuego_targets * (done) add ftc list-nodes * ftc query-target - OK * ftc set * requires putting dynamic variables in a separate file * fuego-rw/boards/bbb-poky-sdk.data * source it at runtime (. /fuego-rw/boards/bbb-poky-sdk.data) * ftc delete * ftc package-test * ftc run-test (without using jenkins node) * ftc list-runs * ftc package-run
|
|
|
=== features === * flot chart is working * plot.png (matplotlib?) is working (OK)
|
|
|
== done == * + modify ftc list-tests to scan board directory instead of jenkins jobs * + create Functional.fuego_board_check * + memory * + storage * + configs (procfs) * + proc entries * + logger status * + recommended DISTRIB (base, nologread, nosyslog) * + programs * + logread, bc, cat, etc. * +transport * + time for transfers
|