timed out s2s bidder prevents auction from completing properly

[jsnellbaker]

Type of issue

bug

Description

While testing fix introduced in #2790 - the following behavior was observed:

• when testing a s2sbidder + client-side bidder and forcing the s2sbidder to timeout (with a small time used in the s2sConfig), the client-side winning ad still appeared on the page but the auction seemed to stop right after the requests were sent out. The console log messages didn't show the normal bids received, putting the keyword data together or executing the bidsBackHandler code.

Steps to reproduce

Setup a s2s config with one bidder (like appnexus) with a small timeout (eg 10). In the adUnits, set it up with a s2s bidder and a client-side bidder.

Load the page and observe the console.

Expected results

Would expect the s2sbidder to timeout and not participate, but the client-side bidder could still win the auction. The auction then would properly close out.

Actual results

The s2sbidder does timeout, and it seems like the client-side bidder does still win the auction (as their ad gets rendered on the page). But like described earlier, the auction seems to finish incompletely (see the sudden cut-off of action in the console logs).

Platform details

1.15 Prebid.js + fix noted above

[jsnellbaker]

this is user-error; not an issue.