action #54008
closed
- Project changed from openQA Infrastructure to openQA Project
- Category set to Support
- Status changed from New to Feedback
- Assignee set to okurz
Are you sure that the label at the front of the line does not change along with the link? Because this is what I observe but you have to carefully look to realize :)
It is true that the order can switch on refresh and also the "default machine type" is computed based on visible results. That is the "feature" about preferred machine types. Imagine the scenario when there are 20 scenarios assigned to "64bit" and only a single one to "uefi" to act as a special scenario then the extension is only displayed for the "…@uefi" case but not for the others. Only in the special case as you have when there are the same amount of scenarios for each machine type the computation can randomly come up with one of the available machine types as the "preferred" one. I guess though making that reproducible as well would be a good feature.
side-question: why do you need the exact amount of test scenarios for each machine, isn't that a bit redundant and wasteful?
I mean test result not alignment to test name, not machine types. Picture has attached for details.
So I dont need the exact amount of test scenarios for each machine, I just used to refresh to check my comments.
Can you try to narrow down the original problem e.g. by limiting the search using one of the available filter settings?
lansuse wrote:
So I dont need the exact amount of test scenarios for each machine, I just used to refresh to check my comments.
Sorry, I missed a word in my question. What I actually meant: What is the benefit of having each test scenario in https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build=0216&groupid=240 at least twice, one time for 64bit and once again for 64bit-smp?
okurz wrote:
Can you try to narrow down the original problem e.g. by limiting the search using one of the available filter settings?
lansuse wrote:
So I dont need the exact amount of test scenarios for each machine, I just used to refresh to check my comments.
Sorry, I missed a word in my question. What I actually meant: What is the benefit of having each test scenario in https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build=0216&groupid=240 at least twice, one time for 64bit and once again for 64bit-smp?
I have try with filter to reduce lines in a page, but still reproduce the issue.
For the two machine types, because their kernel config are different, and we need to cover various senarios, such as cloud user.
- Assignee changed from okurz to lansuse
please update the description of the ticket according to the bug defect template with the most minimal way to reproduce the issue, e.g. a URL pointing to the filtered page where the issue still shows up.
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
- Status changed from Feedback to New
- Assignee changed from lansuse to okurz
- Related to action #16354: Unambiguous lookup of "preferred machine" for same amount of multiple machine types added
- Status changed from New to Feedback
thanks for the update, let's see how it looks after #16354
- Status changed from Feedback to Blocked
That really sounds like an exact duplicate of the issue mentioned by @okurz.
- Status changed from Blocked to Resolved
change from #16354 is effective on both o3 and osd now. I checked the link from the description refreshing and clicking the first link like 10 times and it's unambiguous now.
Also available in: Atom
PDF
