summaryrefslogtreecommitdiff
path: root/ext/googletest/googlemock
diff options
context:
space:
mode:
authorGabe Black <gabeblack@google.com>2018-12-05 18:02:14 -0800
committerGabe Black <gabeblack@google.com>2018-12-10 06:44:43 +0000
commit9c1b329bc62ebf693cc4b23ddc7bd2225ef49e6a (patch)
treef39147117fc4b69313b62aedda0f7b46f9a49b89 /ext/googletest/googlemock
parentd89f712d193dc977a13e937432578ebf03336277 (diff)
downloadgem5-9c1b329bc62ebf693cc4b23ddc7bd2225ef49e6a.tar.xz
systemc: Update test output for longer lived processes.
In the systemc spec, process handles can be invalidated if they have no children and are terminated. The implementation is not required to do so however, and for the sake of simplicity gem5 currently does not. To quote: "When the underlying process instance terminates, if the process instance has no surviving children, an implementation may choose to invalidate any associated process handles, but it is not obliged to do so." Two tests have reference output which is affected by this (legal) difference in behavior. In one case, the test creates new processes which reuse the names of processes that have been terminated. Since gem5 doesn't invalidate the old processes, a standard mechanism is activated which renames the processes to something which is unique. The other test has this same problem, and also prints the hierarchy of processes several times during the test. In that hierarchy, the terminated tests with no live children are still present, where in the old reference output they've been removed. This change updates the reference output to match gem5's behavior. Change-Id: I363448de10080bdce01a4df92f991c67b31a2401 Reviewed-on: https://gem5-review.googlesource.com/c/14919 Reviewed-by: Matthias Jung <jungma@eit.uni-kl.de> Maintainer: Gabe Black <gabeblack@google.com>
Diffstat (limited to 'ext/googletest/googlemock')
0 files changed, 0 insertions, 0 deletions