eb2d8b418c
Code in samples does not follow an standarized format for reporting success or operation failure -- thus we use markup (in file sample.tc) to specify what shall be found in the console to consider execution a success. There is a few functional code modifications that add/extend console messages so verification is possible or easier: - hello_world, synchronization: extend the success message to also print which core is running the testcase - pci_enum: print message on success. Change-Id: Idb6cea03adebe97d97854603f963f4e3d4cb856a Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
16 lines
521 B
Plaintext
16 lines
521 B
Plaintext
# @testcase dynamic
|
|
# d2000 have not enough RAM for this
|
|
# _ctb: there are no configs
|
|
# arduino_101_sss, quark_se_sss_ctb: task_arch.h not found -> micro not supported
|
|
# @targets \
|
|
# board:(?!quark_d2000_crb) \
|
|
# board:(?!quark_se_sss_ctb) \
|
|
# board:(?!quark_se_sss_devboard) \
|
|
# board:(?!quark_se_sss_dvp) \
|
|
# board:(?!quark_se_sss_emu) \
|
|
# board:(?!quark_se_ctb) \
|
|
# board:(?!arduino_101_sss) \
|
|
#
|
|
# @eval console-rx %(console)s:5 task_a: Hello World!
|
|
# @eval console-rx %(console)s:5 task_b: Hello World!
|