On 1/12/2023 10:38 AM, Sebastian Huber wrote:
On 12.01.23 16:52, Kinsey Moore wrote:
Annotation of expected test states with a description could get quite
repetitive, but I suppose that's better than losing the information.
I'm fine with this going in for now with a ticket to address this
issue and we can pull the annotations back in when the ticket is
dealt with.
It could look like this:
SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
actions:
- set-test-state:
- reason: |
expected to fail, don't compile these
state: exclude
tests:
- minimum
- reason: |
tests that are passing intermittently
state: indeterminate
tests:
- psx12
- psxtimes01
- rtmonuse
- rtmonusxtimes01
- sp04
- sp20
- sp68
- sp69
- spcpucounter01
- spedfsched02
- spedfsched04
- sprmsched01
- sptimecounter02
- sptimecounter04
- ttest02
- reason: |
tests that pass nominally, but fail under Qemu when the host is
under
heavy load
state: indeterminate
tests:
- spintrcritical03
- spintrcritical04
- spintrcritical05
build-type: option
copyrights:
- Copyright (C) 2020 On-Line Applications Research (OAR)
default: []
description: ''
enabled-by: true
links: []
type: build
That seems like a reasonable format for test state expectations.
Kinsey
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
