Bing Integration:Admax sloshing shows small difference in the actualDailyBudget in google and bing environments

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 , sloshLimits and admaxBossts 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) do not update the spend values and slosh for the next day's date.

./admax.sh -d5 -T<next day's date> -a<accountId>

6. This sloshes and sets the budget for the next day.

7. Now , in both the DBs (yell-ec-db2 & yell-ec-db1) again update the spend values in (bingMccAdMax & googleMccAdMax respectively) for the third's day date (from first slosh date) and execute admax.sh again:

./admax.sh -d5 -T<third day's date> -a<accountId>

7. Observe the result in the actualDailyBudget and the admaxCarryOvers table in both the environments, 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:

There is a difference of around 0.3 - 0.6 pounds on the pooledCarryover/budget set on third day on comparison.

> Attaching the logs for the third's days slosh