Hi, Vita,
Now I am confused. I know we use the 'arch' here to represent the
architecture of the machine (test server or client).
The architecture I am talking about here is the Fedora system that we
will test. Since I would like
autoqa can cover the test case:
http://fedoraproject.org/wiki/QA:Installer_image_presence_test_case
I would like to check the arch listed in .treeinfo is correct or not,
so we have to tell autoqa which
arch we are testing, then we can compare the real arch with that in
.treeinfo.
If the arch only represent the machine arch, then the option 'arch' in
parser is not useful, since the
arch can be detected by default. Am I right?
Thanks.
Not completely un-useful, since the arch that we detected in the test was
actually the arch of the system running, not necessarily of the actual HW.
So if you were running 32bit system on 64bit, you'd get 32bit there.
Actually, although that is probably exactly the behaviour you want now,
the point of the 'arch' parameter is to pass the actual HW architecture the
test was scheduled to run upon.
I am not sure when it could be needed to know the HW arch really instead
of system arch (esp. should we use 64bit HW to test 32bit Fedora) - so perhaps
it is of little significance right now.
In any way, just using util.get_basearch() should get you the arch you want
(of the system), you are right.
Thanks
Vita