Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: Bing-Integration
-
Component/s: None
-
Labels:None
-
Environment:
--------------------------------------------------
Project: Bing Integration
Bidmgr Build for Bing: tsa-build-bidmgr-2012-03-08-p242-r2154
Bidmgr Build for Google: tsa-build-bidmgr-2012-03-06-p47-r2141
Bing Admax Server: yell-ec-xml2.ri.thesearchagency.com (10.1.30.226)
Google Admax Server: yell-ec-xml.ri.thesearchagency.com (192.168.30.84)
DB: yell-ec-db2 (10.1.30.225)
DB: yell-ec-db1 (192.168.30.83)
--------------------------------------------------
-------------------------------------------------- Project: Bing Integration Bidmgr Build for Bing: tsa-build-bidmgr-2012-03-08-p242-r2154 Bidmgr Build for Google: tsa-build-bidmgr-2012-03-06-p47-r2141 Bing Admax Server: yell-ec-xml2.ri.thesearchagency.com (10.1.30.226) Google Admax Server: yell-ec-xml.ri.thesearchagency.com (192.168.30.84) DB: yell-ec-db2 (10.1.30.225) DB: yell-ec-db1 (192.168.30.83) --------------------------------------------------
Description
Pre-conditons:
1. For testing the sloshing , do the necessary data set-up as mentione din the wiki page - http://kbase.ri.thesearchagency.com/index.php/Bing_Integration_release_notes#Data_setup.
2. Set up an account (2 campaign) in yell-ec-xml for google
3. Set up an account (2 campaign) in yell-ec-xml2 for Bing
4. Ensure the sloshFactor and sloshLimits are same in both the env.
5. Set the damLimit to -1 in Bing environment
Steps:
1. Login to the yell-ec-xml2 & yell-ec-sml system with valid credentials
2. Get inside the jail
3. In both DBs update the same spend values for a date
3. Go to /usr/local/tsa/bidmgr and execute the admax.sh script as follows in both the env:
./admax.sh -d5 -T<date> -a<accountId>
4. This sloshes and sets the budget for the next day.
5. Now , in both the DBs (yell-ec-db2 & yell-ec-db1) again update the spend values in (bingMccAdMax & googleMccAdMax respectively) with the date of the next day.
6. Go to /usr/local/tsa/bidmgr and execute the admax.sh script for the next day's date ,as follows in both the env:
./admax.sh -d5 -T<next day'sdate> -a<accountId>
7. Observe the result in the actualDailyBudget and the admaxCarryOvers table , using the following queries:
SELECT * FROM `st-tracker`.admaxActualDailyBudgets WHERE admaxCampaignID IN (<admaxCampaignIds>);
SELECT * FROM `st-tracker`.admaxCarryovers WHERE admaxCampaignID IN (<admaxCampaignIds>);
Expected Behaviour:
The output of the above query in both the DBs of both the environments should be same.
Actual Behaviour:
The output of the above query in both the DBs of both the environments are not same.
>Attaching the logs from the second run of admax.sh from yell-ec-xml and yell-ec-xml2