#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: Finger Food Component: core | Keywords: -------------------------+-------------------------------------------------- Some tests need to know which architecture to check. But currently we don't pass that information (in the control file). The test can take a guess by detecting operating system architecture (not hardware architecture), but that's an ugly workaround. Pass the architecture info from autoqa script to the test.
#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: Finger Food Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by vhumpa):
What do you mean by this? It looks like 'autoqa' script is already scheduling tests for specific archs to the autotest based on the options passed to it. So the test shouldn't be scheduled to run on an undesired architecture.
So I understand that you mean this: the test is running on desired acrhitecture(s) because it was scheduled to - but it doesn't know on which one, since that information is not passed to it, which is something that 'some' tests need to know.
If I got it right, I'd be glad to do this one among others.
#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: vhumpa Type: enhancement | Status: assigned Priority: major | Milestone: Finger Food Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by vhumpa):
* owner: => vhumpa * status: new => assigned
#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: vhumpa Type: enhancement | Status: assigned Priority: major | Milestone: Finger Food Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by kparal):
The problem was not well described, let me try again:
If the test like is scheduled on some machine, it recognizes the architecture in order to know how to report results (against i686 or x86_64). The problem is the current call os.uname() may return hardware architecture, not software architecture (I believed in that when I reported the ticket, now I'm not sure). We need software architecture of course.
The task therefore is: 1. check what os.uname()[4] returns on 32bit Fedora on 64bit machine 2. if it does not return software architecture, pass the arch to the test as part of autoqa_args 3. if it does return software architecture, think whether it is a better design to pass that information or if current design is good enough
#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: vhumpa Type: enhancement | Status: assigned Priority: major | Milestone: Finger Food Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by vhumpa):
It *seem* to pass the system architecture not the HW one. However, as we aren't sure whether this is always the case, we have decided to pass the arch information to test anyway.
#272: Tell test which arch it is supposed to test -------------------------+-------------------------------------------------- Reporter: kparal | Owner: vhumpa Type: enhancement | Status: closed Priority: major | Milestone: 0.5.0 Component: core | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by kparal):
* status: assigned => closed * resolution: => fixed * milestone: Finger Food => 0.5.0
Comment:
Vhumpa pushed to master as: d65c70786a76016504beeb35841c19b029655fe2
I have amended the documentation: * https://fedoraproject.org/w/index.php?title=Writing_AutoQA_Tests&diff=23... * https://fedoraproject.org/w/index.php?title=Verifying_AutoQA_tests&diff=...
autoqa-devel@lists.fedorahosted.org