DONT test lxc f14 builds on gotan, warhol will do just fine

f14 VMs within a f16 host seem to create issues in the host,
like time moves by as much as 2*diff-with-utc
also we've seen the host's sshd behave oddly. but that might as well
be just a consequence of time shifting

diff --git a/scripts/builds.sh b/scripts/builds.sh
index e77f556..0eee027 100755 (executable)
--- a/scripts/builds.sh
+++ b/scripts/builds.sh
@@ -14,12 +14,10 @@ function velvet () { hostname | grep -q velvet ; }
 #################### lxc on f14 and f16 
 # currently we have the following limitations with lxc
 # initscripts need to be plugged into systemd
-# tcp is not yet available
-liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d lxc -X -f f16 -p linux64 -b @DATE@--lxc16  -e check_initscripts -e check_tcp 
-liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d lxc -X -f f14 -p linux64 -b @DATE@--lxc14  -e check_initscripts -e check_tcp 
-## note that lxc14 is of limited interest
-## all versions check_tcp : this needs port forwarding of some kind regardless of the fedora distro
-#liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d lxc -X -f f14 -p linux64 -b @DATE@--lxc14 -e check_tcp 
+# tcp is not yet available for a lack of port forwarding 
+liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d lxc -f f16 -p linux64 -b @DATE@--lxc16 -X -e check_initscripts -e check_tcp 
+# DONT test this on lxc, this tends to create odd problems with gotan's date and network settings as well
+liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d lxc -f f14 -p linux64 -b @DATE@--lxc14    -e check_initscripts -e check_tcp 
 
 # f12 on reed - no SFA any more
 reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k32-tags.mk -f f12 -p linux64 -b @DATE@--f12-64