Yes, it's a known issue. It basically comes down to the search being funky when: It sees that the product/component exists in the openBenchmarking.org database and sees some information about it, so it's indeed a real/genuine product. But when it then doesn't see any public results available for that component that it knows is real and exists within the database, it tries to expand the scope in case the string format is wrong or reported differently. At the moment then for some products it hits some bogus data. Once there are results viewable for such queries, then it corrects itself.


Reply With Quote
