-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Desktop] Round robin - ad with only parent category is shown once #8971
Comments
@btlechowski @jsecretan |
@tmancey Thanks for checking Check the attached catalog. When it says that
Yet the log shows that the ad was not found. I updated the catalog and renamed the Ads titles so that we can easily check how many times the ad was shown, I renamed the ads to: |
Adding a new TC, it includes Test case: Ads in different categories (child, parent, untargeted) - triggered every 20 minutes
Expected behavior: Ad AAA Ad AAA |
@btlechowski This is correct behaviour based upon priorities as first we choose from parent-child, then from the parent, and then from untargeted |
@tmancey Do you mean TC #8971 (comment)? This TC fails right now, because ad with parent category is shown only once. I added the TC so we can test with it when the issue is fixed. |
Closing issue as resolved by #12486 |
Verification passed on
Verified test plan from the description |
Found when testing #8047
Ads that only have parent category will be shown once:
Ad AAA - shown only once
full category ads will be shown fine
Ad BBB - shown many times
Steps to Reproduce
/usr/bin/brave-browser --enable-logging=stderr --vmodule=brave_ads=3 --brave-ads-staging --rewards=staging=true
cars.com
Note:
Ad AAA
is the one that is shown only onceActual result:
Ad AAA
is shown only onceWhen
Ad AAA
is supposed to be shown in saysFull Log
roundrobinglog2.txt
Expected result:
Ad AAA
andAd BBB
are shown according to Round RobinReproduces how often:
100% repro rate
Brave version (brave://version info)
cc @brave/legacy_qa @rebron @tmancey @moritzhaller @jsecretan
The text was updated successfully, but these errors were encountered: