tests: suppress output on switcheroo tests
Review Request #2058 - Created Oct. 16, 2013 and submitted
| Information | |
|---|---|
| Steve Reinhardt | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9925:a0361278e9b6 --------------------------- tests: suppress output on switcheroo tests The output from the switcheroo tests is voluminous and (because it includes timestamps) highly sensitive to minor changes, leading to extremely large updates to the reference outputs. This patch addresses this problem by suppressing output from the tests. An internal variable can be set to enable the output. Wiring that up to a command-line parameter (perhaps even the rudimantary -v/-q options in m5/main.py).
Issue Summary
1
1
0
0
| Description | From | Last Updated | Status |
|---|---|---|---|
| Could you make this a keyword argument (defaulting to false) to run_test instead? That would allow us to just bind ... | Andreas Sandberg | Oct. 17, 2013, 1:11 a.m. | Open |
Posted (Oct. 17, 2013, 1:12 a.m.)
Thanks for looking into this. I don't really have a strong opinion about the comments below, fix them if you agree, otherwise, just push the change anyway.
-
src/python/m5/simulate.py (Diff revision 1) -
This should be in a separate commit.
-
tests/configs/switcheroo.py (Diff revision 1) -
Could you make this a keyword argument (defaulting to false) to run_test instead? That would allow us to just bind that argument when setting up individual test cases.
Ship It!
Ship It!