* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/minor-timing: FAILED!
* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/o3-timing: FAILED!
* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/simple-atomic: FAILED!
*
Hi all,
I’ve just pushed a patchset which removes the current testing implementation
and replaces it with a work in progress test framework. This framework is meant
to be a strong starting point for a new testing infrastructure which would
allow for more test coverage and an easier/better user
Hello Jason Lowe-Power, Andreas Sandberg,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/4001
to look at the new patch set (#10).
Change subject: cpu, config: Add setFutureCPU to BaseCPU
Hello Jason Lowe-Power,
I'd like you to do a code review. Please visit
https://gem5-review.googlesource.com/4400
to review the following change.
Change subject: python: Add a function to delete references to a SimObject
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/4424
Change subject: tests: Restore a legacy atomic test.
..
tests: Restore a legacy atomic test.
This commit acts as an example for
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/4420
Change subject: tests: Remove the old testing system and all tests
..
tests: Remove the old testing system and all tests
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/4423
Change subject: tests: Add test for the m5-exit instruction.
..
tests: Add test for the m5-exit instruction.
Change-Id:
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/4422
Change subject: tests: Add a simple example test
..
tests: Add a simple example test
Change-Id:
I haven't had a chance to look at any of the documentation you referenced
and am generally in favor of improvements to our testing setup, but it
might be a bit premature to delete the old system if the new one is still a
work in progress. That would take us from a not that great testing system
to
Hi folks. I'm doing some work on our internal config scripts, and I notice
in Simulation.py in scriptCheckpoints, there are some format strings
("cpt.%d" specifically) which don't have any arguments. I *think* this code
is being called, and I also think that somehow %d is being substituted with
10 matches
Mail list logo