{{TableOfContents}}

These are the Release Notes for the Fuego 1.6 (Glow) release.

See [[Release 1.6 testing]] for some notes about test status.

= Major changes =
The major changes to Fuego in this release are as follows:
 * suppport for default_board
 * add support for short test names
 * added support for "match_board" option in chart_config

= Details =
== default_board ==
The fuego.conf file supports a new option, called 'default_board'.
If this configuration option is set, then when 'ftc' is used
without specifying a board, the value for default_board is used
instead.

This can be used to execute tests on a particular, designated
board with less typing. For example:

if fuego.conf has the line:
{{{#!YellowBox
default_board=local
}}}

they you can type:
{{{#!YellowBox
$ ftc run-test -t hello_world
}}}

Instead of the more verbose
{{{#!YellowBox 
$ ftc run-test -b local -t hello_world
}}}

This can be useful if you only have a single board in your lab,
or you are installing and using Fuego natively (for local access).
 
Note that you can achieve the same by defining the FUEGO_BOARD
environment variable to "local", but specifying a default_board
in the config file is a bit easier.  If a default board is
specified using the FUEGO_BOARD environment variable,
that takes precedence over the value specified in the fuego.conf
file.


== short test names ==
ftc has been modified to allow the use of short test names.  Instead
of having to type "Functional.LTP" as the test name, you can now
omit the "Functional" or "Benchmark" prefix, and just use "LTP".  This
will work as long as the test name short name is unambiguous.  If
the same test name is available as both a Benchmark and Functional test
(like netperf), then you have to use the full test name.

Note that the bash completion was updated to support short test names.
You can type 'ftc run-test -b board1 -t hello<tab>', and the shell will
complete the short test name for you (to 'hello_world').

== match_board chart_config option ==
A user can now specify that the results displayed on a Jenkins job
page for a job are restricted to just the results for the board
associated with the job.

By default, Fuego has Jenkins show the test results for all of the boards
that a test has run on.  By setting "match_board" to "true" in the
chart_config.json file for a test, only the results that match the
board for the job will be displayed.

For example, for the test Functional.hello_world, if you have jobs
for the boards 'bbb', 'rp4', and 'ren1', then you would have the following
jobs defined in Jenkins:
 * bbb.default.Functional.hello_world
 * rp4.default.Functional.hello_world
 * ren1.default.Functional.hello_world

The test results for all of these boards would be shown on the job page
for all of these jobs.  However, by adding this line to the chart_config.json
file for Functional.hello_world (in the section "chart_config")

{{{#!YellowBox
  "match_board": "true"
}}}

then on the bbb.default.Functional.hello_world job page, only the test
results for the 'bbb' board will be shown.

= Change details =


= fuego git log items =
Number of commits since v1.5.0 = 153

( $ glog -v -n 1000 --since=2019-08-14 )

 * (note) change docs to reStructuredText format
 * (note) use readthedocs.io for online documentation
 * add packages to docker container to support selenium
 * set more jenkins plugin versions to fixed values



= fuego-core git log items =
Number of commits since v1.5.0 = 322

 * improved fuego_board_function_lib.sh
   * (doc) document fuego_board_function_lib.sh
 * (note) new tests or testcases:
   * ltrace, nfs, lvm, sysvinit, filesystem_compare, initscripts
   * logrotate, checkmounts, net-snmp, 
 * test improvements:
   * LTP
     * improve auto-skipping of tests
     * improve results parser
     * (note) support more recent version of LTP test suite
     * (note) (doc) add Functional.LTP_one_at_a_time
   * (note) iozone - update to version 492
   * (note) add lots of test.yaml files (for binary packages)
 * (note) (doc) support use of python3 as python interpreter
 * (note) (doc) config supports
   - 'default_board'
   - 'use_binary_packages'
   - 'auto_install_tests'

 * (note) continuing support for server-based operations (fserver)
   - new 'query-request' command
   - new 'get-run' command
   - new 'put-board' command
   - new 'install-run' command
   - new 'update-board' command
   - support for '--remote' for several commands
   - improve poll_requests.sh
     - add duration argument

 * (note) more support for binary packages
   - support --binary in ftc package-test, list-tests, install-test

 * ttc:
   - (doc) query-board supports '--sh'
   - (+note) (doc) short test names
 
 * core:
   - (doc) add board-cmd.sh script
   - (doc) add deorphan-runs.py script
   - (note) use less operations on target during test execution
   - new FUEGO vars for tests script to control execution:
     - (note) (doc) add support for NO_BOARD_TESTLOG (to quiet a run-test warning)
     - (note) (doc) support FUEGO_CMD_TIMEOUT and FUEGO_CMD_TIMED_OUT, and FUEGO_CMD_DURATION
       - allows timing/timeout of 'cmd' function calls
       - this is used by Functional.LTP_one_at_a_time
   - (note) (doc) support timeout option in spec file, for timeout for an individual test variant (spec)
 * (note) support other transport tools:
   - (doc) support ebf
   - (doc) support lc
   * support new board vars:
     - (doc) BF_NAME = board farm name

 * (note) support mostlynull distribution overlay (fuegoclass)
 * parser:
   - (doc) add a TAP parser.py as a reference parser

 * debug helpers:
   - (note) (doc) add test-parser.sh