🐛Update Ooyala player version from Sandbox to Prod

[bc-vescoto]

The Ooyala player iframe version currently used is at https://player.ooyala.com/static/v4/sandbox/amp_iframe/skin-plugin/amp_iframe.html which is using the player version 4.10.6

Our current production version is at v4.32.8. This update will solve some customer issues with analytics and provide them with a more recent and stable player.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[amp-owners-bot]

Hey @alanorozco, these files were changed:

• extensions/amp-ooyala-player/0.1/amp-ooyala-player.js

Hey @wassgha, these files were changed:

• extensions/amp-ooyala-player/0.1/amp-ooyala-player.js

Hey @ampproject/wg-caching, these files were changed:

• extensions/amp-ooyala-player/0.1/test/validator-amp-ooyala.html

[bc-vescoto]

@googlebot I signed it!

[bc-vescoto]

@googlebot I signed it!

[bc-vescoto]

@googlebot I signed it!

@googlebot I signed it!

[bc-vescoto]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@googlebot I signed it!

[bc-vescoto]

@wassgha I see that it did not pass the Travis CI verification. Is something else that requires to be updated?

Seeing the following warning:

DeprecationWarning: assert.fail() with more than one argument is deprecated. Please use assert.strictEqual() instead or only pass a message.

ValidatorFeatures amp-ooyala-player/0.1/test/validator-amp-ooyala.html Message: AssertionError [ERR_ASSERTION]: amp-ooyala-player/0.1/test/validator-amp-ooyala.out:1:0

[wassgha]

@wassgha I see that it did not pass the Travis CI verification. Is something else that requires to be updated?

Seeing the following warning:

DeprecationWarning: assert.fail() with more than one argument is deprecated. Please use assert.strictEqual() instead or only pass a message.

ValidatorFeatures amp-ooyala-player/0.1/test/validator-amp-ooyala.html Message: AssertionError [ERR_ASSERTION]: amp-ooyala-player/0.1/test/validator-amp-ooyala.out:1:0

Hey! You need to run gulp validator --update_tests in order to update the output of the validator test you changed to match the changes you made. Once the .out file is updated, please commit and push it :)

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[bc-vescoto]

@googlebot I fixed it.

[bc-vescoto]

@googlebot I fixed it.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[bc-vescoto]

@wassgha Hi! I just want to confirm if something is still missing since the merging is still blocked for me. Is this only can be done by authorized users? Thank you!

[wassgha]

Once #24828 lands, the owners check on PRs like this would pass. Merging for now.