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 have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

Seems like there are 2 users involved in this. Make sure your GitHub account's email and your .gitconfig's [user] is the same user.

@xster Am I right in thinking I can view that by running this:
git config --list ?
I can't any see emails after running that command so I'm guessing I need to add it by doing something like this:
git config --global user.email "[email protected]"
After doing that will I need to raise a new PR?

The author field on the commit seems to end with "MacBook-Pro.local". I guess it made that up based on your username/machine name because you hadn't configured any. The command you gave above will fix this for future commits, but you'll need to fix this commit, which I think you can do with:

git commit --amend --author="Author Name <[email protected]>"

Then you'd have to force push (be careful doing this, if done in the wrong place or from the wrong branch, you could lose work).

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

These tests were passing before I changed the author on the commit, is it because the build went down? If so how do I get the tests to run again?

The failed tests looked like infrastructure issues (io errors/failed to launch instances) so I've restarted them.

@DanTup Thanks, for future reference how did you do that?

@Robiquet it requires committer access to this repo (there is a re-run button on the Cirrus pages). Another way to do it would be to just push an empty commit commit (for ex. git commit --allow-empty -m "Force build" && git push).

I think you resolved the comments but forgot to push your newest commits :)