| commit | fbbf6cbecfa49fa7b571bffd1d859f529eb4e586 | [log] [tgz] |
|---|---|---|
| author | Srikrishna Iyer <sriyer@google.com> | Wed Aug 05 23:00:51 2020 -0700 |
| committer | sriyerg <46467186+sriyerg@users.noreply.github.com> | Thu Aug 06 12:50:13 2020 -0700 |
| tree | 5bc530bdc8c995a8f0fd421e6baa09b236bf9dc6 | |
| parent | 9ddf230cbb1bd043fa2c8627bf3c1e03de9ccda7 [diff] |
[dvsim] Update `tests` key behavior in regressions This was encountered in #3040. The `common_sim_cfg.hjson` adds a `sanity` regression target without specifying the `tests` key, with the assumption that each individual IP's cfg hjson will update the `sanity` regression with the required list of tests. In PR #3040, the sanity tests in some of the IPs had to be commented out due to some other issues. But on doing so, running `sanity` regression ended up adding ALL available tests for regression for that particular DUT, since the `tests` key remained empty list (originally intended behavior). This PR fixes that behavior. So to sum up: Previous behavior of the `tests` key was as follows: - `tests` member of class `Regression` in `Modes.py` defaulted to empty list - If in regressions (in the hjson), it continues to remain an empty list after all hjson source are parsed, then ALL available tests are run New behavior is as follows: - `tests` member of class `Regression` in `Modes.py` now defaults to `None` - If in regressions (in the hjson) it is set to an empty list, and eventually remains an empty list after all hjson sources are parsed, then no tests are run - If in regressions (in the hjson) it is entirely omitted, such that after all hjson sources are parsed, it continues to hold the value of `None`, the ALL available tests are run Signed-off-by: Srikrishna Iyer <sriyer@google.com>
OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.
This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.
The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.
Have a look at CONTRIBUTING for guidelines on how to contribute code to this repository.
Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).