-# 2.6.27 kernel on f14 - this fails for now - try both archs
-# try on velvet that has a hacked util-vserver
-velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f14 -p linux32 -b @DATE@--k27-f14-32
-velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f14 -p linux64 -b @DATE@--k27-f14-64
-
-# 2.6.27 kernel on f12
-liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f12 -p linux32 -b @DATE@--k27-f12-32 -c dual
-#liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f12 -p linux64 -b @DATE@--k27-f12-64 -B
-
-#### 2.6.22 kernel on f12 - known to be broken, node won't fly
-####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f12 -p linux32 -b @DATE@--k22-f12-32
-####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f12 -p linux64 -b @DATE@--k22-f12-64 -B
-
-# 2.6.22 kernel on f8
-reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f8 -p linux32 -b @DATE@--k22-f8-32 -c dual
-#reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f8 -p linux64 -b @DATE@--k22-f8-64 -B
+# the tests flavours available
+# -B means no test
+# default for the tests setup is one myplc
+# -c dual has two myplc's - pointing to each other AMs
+# -c triangle has three - ditto
+# -c sfamesh makes them point to SMs