@@ -485,6 +485,14 @@
"MACHINE" : "qemux86",
"TEMPLATE" : "altcfg-qemu"
},
+ "qemux86-ptest" : {
+ "MACHINE" : "qemux86",
+ "TEMPLATE" : "ptest-qemu"
+ },
+ "qemux86-ptest-fast" : {
+ "MACHINE" : "qemux86",
+ "TEMPLATE" : "ptest-qemu-fast"
+ },
"genericx86" : {
"MACHINE" : "genericx86",
"TEMPLATE" : "arch-hw",
@@ -181,6 +181,11 @@ case "$target" in
sha256sums $TMPDIR/deploy/images/qemux86
cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/qemux86/*qemux86* $DEST/machines/qemu/qemux86
;;
+ "qemux86-ptest")
+ mkdir -p $DEST/machines/qemu/qemux86
+ sha256sums $TMPDIR/deploy/images/qemux86
+ cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/qemux86/*qemux86* $DEST/machines/qemu/qemux86
+ ;;
"genericx86")
mkdir -p $DEST/machines/genericx86
sha256sums $TMPDIR/deploy/images/genericx86
This will be particularly useful for testing Y2038 issues, as that is the only 32 bit target that can be run at native speed on the AB cluster. Whether a-full should get fast ptests or full ptests can be decided after collecting AB execution times for both. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> --- config.json | 8 ++++++++ scripts/publish-artefacts | 5 +++++ 2 files changed, 13 insertions(+)