Age | Commit message (Collapse) | Author |
|
Change-Id: If48393a64061502ffc1651e39ef5ef55801c19d2
|
|
We are accumulating local toolchain copies (via rsync currently),
leading to disk full issues.
We can remove them after the benchmark completed.
The current patch does not delete the toolchain if the benchmark
failed, because we run under 'set -e', and thus we exit/execute the
trap handler before removing the toolchain.
Change-Id: Ie52bf3498118046d057093c9db39763c44f1b0c1
|
|
Change-Id: I4331cededc199656e0e8f0981073f6ea1af61ef8
|
|
In case we need to copy the toolchain to the "run" container,
we need to start it early.
Change-Id: Iafcea3ecbb3d2d080f5a18d80f63205b39abc490
|
|
Change-Id: Ia3c43e754e6e3f3f13c1e00eab64ab8aa880148d
|
|
Re-adding tcwg-benchmark causes an error, so create $USER in the
container only if it is not tcwg-benchmark.
Another option would be to change new-user.sh (in dockerfiles repo) to
automatically switch to update mode when it detects that the new user
is already defined, but that seems to be in contradiction with
new-user.sh --update flag.
Change-Id: Ib1cccd931cbae3889bb96dec16b65cf1f9314416
|
|
Change-Id: Ice790451e133767663ec93f8cbe73983ea70e70b
|
|
Starts a container with access to USB devices to build and run
benchmarks on boards in bare-metal mode.
Currently supports coremark only.
Change-Id: I19876d32fc3c2b3322960f86798dc02a96aed25b
|