zephyr/scripts
Andy Ross 5efdd6a525 sanitycheck harness: Correct ordered regex handling
The way sanitycheck did its ordered regexes is that it would test
every regex against every line, and store the matching lines and their
regexes in an OrderedDict and check that they happened in the right
order.

That's wrong, because it disallows matching against a line that
previously appeared (and should have been ignored) in the input
stream.  The watchdog sample is the best illustration: the first boot
will (by definition) contain all the output already, but the regex has
to match against a line from the SECOND boot and not the same one it
saw earlier.

Do this the simple way: keep a counter of which regex we're trying to
apply next and increment it on a match.  This is faster too as we only
need to check one pattern per line.

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-06-19 14:37:20 -04:00
..
checkpatch
ci
coccinelle
dts
footprint
gitlint
kconfig
sanity_chk
support
west_commands
.gitignore
check_link_map.py
checkpatch.pl
checkstack.pl
coccicheck
dir_is_writeable.py
elf_helper.py
file2hex.py
filter-known-issues.py
gen_app_partitions.py
gen_cfb_font_header.py
gen_gcov_files.py
gen_kobject_list.py
gen_offset_header.py
gen_priv_stacks.py
gen_relocate_app.py
gen_syscall_header.py
gen_syscalls.py
mergehex.py
parse_syscalls.py
process_gperf.py
qemu-machine-hack.py
requirements.txt
sanitycheck
series-push-hook.sh
spelling.txt
subfolder_list.py
tags.sh
valgrind.supp
waitpid
west-commands.yml
zephyr_module.py