This make it easier for non-privileged users to run tests automatically.
The tests requiring sudo are flagged using a mechanism inspired by
the autopkgtest system in Debian, where a control file contain
information about the test. All tests requiring sudo get a
'sudo' flag in the Restrictions field there.
Also add reporting on number of skipped tests at the end.
Users using twopass processing request increased number of
named component instances (typically for simple logic elements
like and2,or2,...). This commit removes the maximum
limit of 16 for names= items for realtime components.
Notes:
1) For realtime components (loadrt), the maxium number of
names= items is not limited by halcompile.
2) For userspace components (loadusr), the maximum number
of names= remains fixed at: MAX_USERSPACE_NAMES=16
3) The maxium number of personalities is by default:
MAX_PERSONALITIES=16
4) A command line option can set the maximum number of
personalities: -P|--personalities
5) Behavior for count= directives is unchanged.
6) Current MAX_CMD_LENGTH=1024 in src/hal/halcmd.h may
need increasing if using many very long names= names.
7) For normal usage, all names= items (comma-separated)
must (still) be on a single loadrt line. Using twopass
processing allows multiple loadrt lines for the same
component type.
8) Formerly, a loadrt directive that specified no count= parameter
and an empty names= parameter resulted in an error and no
component was loaded. With this commit, such a directive
loads a single instance (like and2.0)
Updated tests/:
a) module-loading/or2/17-names ---- remove, no longer applicable
b) module-loading/or2/0-names ---- adapt per Note 8 above
c) module-loading/pid/17-names ---- no change (pid.c hardcoded for 16)
d) module-loading/siggen/17-names - no change (siggen.c hardcoded for 16)
e) halcompile/personalities_mod --- new tests for personalites that are
modulo the compiled-in personalities
using the --personalities= option
This is currently accepted, and results in a single component with no
name. HAL objects like pins and functions get names like ".pin-name"
and ".func", which seems kind of bogus.
This is probably a bug, but we shouldn't change it in 2.6. We should
probably change 2.7 to reject this.
Signed-off-by: Sebastian Kuzminsky <seb@highlab.com>
There is no upper limit on counts= like there is on names=. This tests
counts=1, =16, and =17, they're all accepted.
Signed-off-by: Sebastian Kuzminsky <seb@highlab.com>
Each test case in this suite used to have its own copy of the pin
name regex, but it's enough to have one for 'names' loads and one for
'num_chan' loads.
