I would rather we not start depending on pytest. Just my take.There's
a difference between a utility for one chipset and global
infrastructure, and pytest could become the latter.
There's a pretty big testing activity starting up in OCP, involving
many companies, and python is not something we
Am Fr., 15. Okt. 2021 um 19:50 Uhr schrieb Ricardo Quesada <
ricar...@google.com>:
> In the meantime, would it make sense, as Jack mentioned, to land my change
> [1] as it is? It is small/simple and it only has ~160 LoC Python.
> For comparison, other util are using Python: util/qualcomm has
Thanks for the answers!
Regarding the end-to-end testing framework, perhaps that's a topic that
needs further discussion / consensus (?). E.g:
- discuss policy: what parts of coreboot should have end-to-end testing.
Should it be forced? recommended? optional?
- do some requirement gathering:
Hi,
Please find the latest report on new defect(s) introduced to coreboot found
with Coverity Scan.
1 new defect(s) introduced to coreboot found with Coverity Scan.
1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s)
4 matches
Mail list logo