video.cloud-client.analyze.video_detect_faces_beta_test: test_detect_faces failed

[flaky-bot]

This test failed!

To configure my behavior, see the Build Cop Bot documentation.

If I'm commenting on this issue too often, add the buildcop: quiet label and
I will stop commenting.

---

commit: d85e2ca
buildURL: Build Status, Sponge
status: failed

Test output

Traceback (most recent call last):
  File "/workspace/video/cloud-client/analyze/video_detect_faces_beta_test.py", line 33, in test_detect_faces
    assert "Attributes:" in out
AssertionError: assert 'Attributes:' in '\nProcessing video for face detection annotations.\n\nFinished processing.\n\nFace detected:\nFace detected:\nFace de...ted:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\n'

[danoscarmike]

Reproducing this locally. It's also blocking migration of these samples to googleapis/python-videointelligence (e.g. googleapis/python-videointelligence#51).

I'm wondering if it would be sufficient to assert that the response body is has an annotation result, albeit empty?

[telpirion]

I think that's the right approach, although it makes me a little nervous to say that our service tests don't expect the services to say anything.

[flaky-bot]

commit: 85ea173
buildURL: Build Status, Sponge
status: failed

Test output

Traceback (most recent call last):
  File "/workspace/video/cloud-client/analyze/video_detect_faces_beta_test.py", line 33, in test_detect_faces
    assert "Attributes:" in out
AssertionError: assert 'Attributes:' in '\nProcessing video for face detection annotations.\n\nFinished processing.\n\nFace detected:\nFace detected:\nFace de...ted:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\nFace detected:\n'

[danoscarmike]

@telpirion, I hear you. In this case it's not saying nothing - we at least get the "face detected" but it's flaky on whether it returns additional annotations. I'll make a PR.