----- Original Message -----
I will add the following
cmd += " --arch=%s" % kwargs['arch']
OK, then it makes sense.
since the install.py also have the option --arch, the default is
x86_64.
The default seems to be the machine (operating system) architecture. If you run it on
x86_64, it should return x86_64. If you run it on i386, it should return i386.
One thing I am still not very clear, do we have both x86_64 and i386
servers to run
x86_64 and i386 Fedora respectively?
You mean "machines/clients" instead of "servers", right? We have one
autotest server (
autoqa.fedoraproject.org), but many test clients with different
architectures.
I think we will use x86_64 to run
both x86_64 and
i386 Fedora during the development. So it would be better to split the
server
and the Fedora tested architectures, the server architecture can be
detected by default,
the architecture of Fedora tested will be passed as a parameter. What
do you think?
Exactly, that's also my view.
But it will take some time to implement it. In the meantime, you can do one of these
workarounds:
1. don't run the test locally, but schedule it through autotest server (provided that
you have more physical machines available, since rats_install requires a physical
machine)
2. don't use kwargs['arch'] temporarily, but instead parse the compose URL
(e.g. [1]) and take the test architecture from that.
[1]
http://download.englab.nay.redhat.com/pub/fedora/linux/releases/14/Fedora...
Does it help?