[RTEMS Project] #3151: Should Tests Be Added to .tcfg file Which Only Fail to Link with RTEMS Debug is Enabled?

[RTEMS trac]

#3151: Should Tests Be Added to .tcfg file Which Only Fail to Link with RTEMS
Debug is Enabled?
---------------------------+------------------------------
 Reporter:  Joel Sherrill  |       Owner:  joel.sherrill@…
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  testing        |     Version:  4.12
 Severity:  normal         |  Resolution:
 Keywords:                 |
---------------------------+------------------------------

Comment (by Chris Johns):

 It would mean some attribute, tag or grouping would need to be added to
 the `.tcfg` files. The `.tcfg` processing is now in Python so this makes
 that side of things easier to implement. I suggest we add groupings. For
 example:

 {{{
 [default]
  exclude: fileio
  exclude: cdtest
  exclude: iostream
  exclude: flashdisk01

 [debug]
  exclude: jffs2_fspermission
  exclude: jffs2_fsrdwr

 [smp]
  exclude: pppd

 [smp-debug]
  exclude: utf8proc01
 }}}

 There are some issues we need to decide on or solve:

  1. Which build options do we create variants for? We should formalize
 these.
  2. How would combinations of variant options be handled? For example is a
 test in the `debug` group not built for any //debug// variant such as
 `smp-debug`?
  2. How do we perform the `make` level processing in
 [https://git.rtems.org/rtems/tree/testsuites/automake/subdirs.am
 testsuites/automake/subdirs.am] to create a suitable list of variants?

--
Ticket URL: <http://devel.rtems.org/ticket/3151#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project