[coreboot-gerrit] Patch merged into coreboot/master: util/mma: Add tools to support (semi) automation test of mma

[gerrit at coreboot.org]

the following patch was just integrated into master:
commit 0175fb1b4ffaa126df516a0086e5adb51cfc94e2
Author: Pratik Prajapati <pratikkumar.v.prajapati at intel.com>
Date:   Wed Nov 18 15:02:19 2015 -0800

    util/mma: Add tools to support (semi) automation test of mma
    
    mma_automated_test.sh takes a config file (/usr/local/mma/tests) as
    input and executes all tests mentioned in the config file.
    
    format of the config file is one or more lines mentioned below.
    
    	<MMA test name> <MMA test param> <#count>
    
    e.g. consider following config file.
    
    	Margin1D.efi Margin1DRxVrefConfig.bin 4
    	RMT.efi RMTConfig.bin 1
    	MarginMapper.efi ScoreTxVref-TxDqDelayConfigCh1.bin 2
    	Margin2D.efi Margin2D_Cmd_Ch0_D1_R0_Config.bin 3
    
    This will execute Margin1D.efi MMA test 4 times with
    Margin1DRxVrefConfig.bin param and results will be stored
    in DUT under /usr/local/mma/results_<date-time-stamp>
    with Margin1D_Margin1DRxVrefConfig_1.bin to
    Margin1D_Margin1DRxVrefConfig_4.bin name.  Subsequently all tests
    will be executed and results will be stored.
    
    /etc/init/mma.conf invokes mma_automated_test.sh when DUT
    starts. And if valid test config is preset at /usr/local/mma/tests,
    mma_automated_test.sh will continue executing the tests.  Each time
    DUT will be rebooted and next test in sequence will be executed.
    
    Overall follow these steps to start MMA.
    (1) create /usr/local/mma/tests file with the syntax mentioned above.
    (2) either reboot the DUT (mma.conf will be called at each boot time,
    which would run the mma_automated_test.sh) or execute "start mma"
    command (to save a reboot cycle.)
    (3) all test results can be found under
    /usr/local/mma/results_<date-time-stamp> where <date-time-stamp> is
    YY_MM_DD_HH_mm format (YEAR_MONTH_DAY_HOUR_MINUTE) when you started
    the mma tests.
    
    BRANCH=none
    BUG=chrome-os-partner:43731
    TEST=Build and Boot kunimitsu (FAB3). MMA automation tests executes
    and results get saved.
    
    Change-Id: I6805fdb95b7ff919f9c8e967b748e4893a3f9889
    Signed-off-by: Patrick Georgi <pgeorgi at chromium.org>
    Original-Commit-Id: 68c0a531ba3fc335b92b17002e75412195b778c4
    Original-Change-Id: I92db7ca47e1e3e581c3fbb413f11e2c3e6d19b6b
    Original-Signed-off-by: Pratik Prajapati <pratikkumar.v.prajapati at intel.com>
    Original-Signed-off-by: Icarus Sparry <icarus.w.sparry at intel.com>
    Original-Reviewed-on: https://chromium-review.googlesource.com/313180
    Original-Commit-Ready: Pratikkumar V Prajapati <pratikkumar.v.prajapati at intel.com>
    Original-Tested-by: Pratikkumar V Prajapati <pratikkumar.v.prajapati at intel.com>
    Original-Reviewed-by: Aaron Durbin <adurbin at chromium.org>
    Original-Reviewed-by: Pratikkumar V Prajapati <pratikkumar.v.prajapati at intel.com>
    Reviewed-on: https://review.coreboot.org/12928
    Tested-by: build bot (Jenkins)
    Reviewed-by: Stefan Reinauer <stefan.reinauer at coreboot.org>


See https://review.coreboot.org/12928 for details.

-gerrit