Release_1.2_To_Do 

Fuego 1.2 wiki

Login

Release 1.2 To Do

priorities for 1.2 release [edit section]

Free form list of items to do: [edit section]

  • add checkbox and replot to flot plots? (maybe not)
  • document parser:parse_log and parser:common

    Documentation [edit section]

    Here are things needing documentation:
    • parser:parse_log
    • parser:common
    • per_job_build variable in spec files
    • document new APIS
      • function_is_on_sdk

    What's left to do (tasks) [edit section]

    item  ^ priority  ^ status  ^ notes  ^
    Update wiki documentation for this release high open In particular, update information about results files, main.sh, spec file format, testplan defaults
    automatically create a view for each board medium open use a command line option on fuego add-nodes (--make_view)
    fix LTP high open make sure LTP works for docker and bbb
    support AGL/JTA reports high open Song Cai is interested in this work
    support unified output format high open create results.json files for all tests (including functional tests) see Unified_Results_Format_Project
    Edit the data below.

    Stuff that got deferred [edit section]

    item  ^ priority  ^ status  ^ notes  ^
    Benchmark job created without a testplan has no plot link medium defer If you create a Benchmark job (say Benchmark.fuego_check_plots) using ftc add-jobs -b docker -t Benchmark.fuego_check_plots -s default, then build page for this job will have no link to plot.png
    handle set -e differently medium defer handle script errors explicitly, instead of relying on shell
    handle timeouts automatically medium defer should be in test and board, not in plan - but depends on spec, transport, build time etc
    support LAVA transport high defer Required for AGL/JTA integration
    support phase reordering low defer May be useful for LAVA integration (don't want to run pre_test before build)
    support separate build phase medium defer don't want to hold board reserved during build, for lava integration and handling timeouts better
    web file transport low defer could be useful for some interesting target cases
    Edit the data below.

    Full table [edit section]

    item  ^ priority  ^ status  ^ notes  ^
    Benchmark job created without a testplan has no plot link medium defer If you create a Benchmark job (say Benchmark.fuego_check_plots) using ftc add-jobs -b docker -t Benchmark.fuego_check_plots -s default, then build page for this job will have no link to plot.png
    Issue_0048 high closed problem with LTP and libaio-dev installation (one toolchain overwrites another toolchains libaio.so symlink (see Issue_0048)
    Update wiki documentation for this release high open In particular, update information about results files, main.sh, spec file format, testplan defaults
    automatically create a view for each board medium open use a command line option on fuego add-nodes (--make_view)
    fix LTP high open make sure LTP works for docker and bbb
    fix ftc device dictionary medium closed used for board check and pre-populating options
    get rid of nbench-bytes medium closed This is a dumb duplicate of nbench_bytes (see Fuego naming rules)
    handle set -e differently medium defer handle script errors explicitly, instead of relying on shell
    handle timeouts automatically medium defer should be in test and board, not in plan - but depends on spec, transport, build time etc
    modify ftc run-test for base script calling convention high closed call main.sh instead of base script, and set TESTDIR and TESTNAME
    ov_transport_connect/ov_transport_disconnect high closed Sounds like Jan-Simon will do it
    support AGL/JTA reports high open Song Cai is interested in this work
    support LAVA transport high defer Required for AGL/JTA integration
    support phase reordering low defer May be useful for LAVA integration (don't want to run pre_test before build)
    support separate build phase medium defer don't want to hold board reserved during build, for lava integration and handling timeouts better
    support unified output format high open create results.json files for all tests (including functional tests) see Unified_Results_Format_Project
    web file transport low defer could be useful for some interesting target cases

    Data [edit section]

    Edit the data here:
    item  ^ priority  ^ status  ^ notes  ^
    Benchmark job created without a testplan has no plot link medium defer If you create a Benchmark job (say Benchmark.fuego_check_plots) using ftc add-jobs -b docker -t Benchmark.fuego_check_plots -s default, then build page for this job will have no link to plot.png
    Issue_0048 high closed problem with LTP and libaio-dev installation (one toolchain overwrites another toolchains libaio.so symlink (see Issue_0048)
    Update wiki documentation for this release high open In particular, update information about results files, main.sh, spec file format, testplan defaults
    automatically create a view for each board medium open use a command line option on fuego add-nodes (--make_view)
    fix LTP high open make sure LTP works for docker and bbb
    fix ftc device dictionary medium closed used for board check and pre-populating options
    get rid of nbench-bytes medium closed This is a dumb duplicate of nbench_bytes (see Fuego naming rules)
    handle set -e differently medium defer handle script errors explicitly, instead of relying on shell
    handle timeouts automatically medium defer should be in test and board, not in plan - but depends on spec, transport, build time etc
    modify ftc run-test for base script calling convention high closed call main.sh instead of base script, and set TESTDIR and TESTNAME
    ov_transport_connect/ov_transport_disconnect high closed Sounds like Jan-Simon will do it
    support AGL/JTA reports high open Song Cai is interested in this work
    support LAVA transport high defer Required for AGL/JTA integration
    support phase reordering low defer May be useful for LAVA integration (don't want to run pre_test before build)
    support separate build phase medium defer don't want to hold board reserved during build, for lava integration and handling timeouts better
    support unified output format high open create results.json files for all tests (including functional tests) see Unified_Results_Format_Project
    web file transport low defer could be useful for some interesting target cases
    Query

  • TBWiki engine 1.9.1 by Tim Bird