IMPORTANT DEBUGGING NOTE: batches of tests are run inside their
own process. For debugging a test inside a debugger, use the
--gtest_filter=<your_test_name> flag along with
--single-process-tests.
Using sharding settings from environment. This is shard 0/1
Using 1 parallel jobs.
Note: Google Test filter = H264DecoderTest.UnvalidatedFirstMbInSliceReachesAccelerator
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from H264DecoderTest
[ RUN      ] H264DecoderTest.UnvalidatedFirstMbInSliceReachesAccelerator

GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
../../media/gpu/h264_decoder_unittest.cc:189:
    Function call: CreateH264Picture()
          Returns: 0x7d8515807680
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/main/docs/gmock_cook_book.md#knowing-when-to-expect-useoncall for details.

GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
../../media/gpu/h264_decoder_unittest.cc:192:
    Function call: SubmitFrameMetadata(0x7dc5157f3680, 0x7d55157f6880, @0x7d65157e35c8 32-byte object <00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 10-00 00-00 00-00 00-00>, @0x7d65157e35f8 {}, @0x7d65157e3610 {}, @0x7d65157e3628 {}, 0x7d8515807680)
          Returns: 4-byte object <00-00 00-00>
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/main/docs/gmock_cook_book.md#knowing-when-to-expect-useoncall for details.

GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
../../media/gpu/h264_decoder_unittest.cc:194:
    Function call: SubmitDecode(0x7d8515807680)
          Returns: 4-byte object <00-00 00-00>
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/main/docs/gmock_cook_book.md#knowing-when-to-expect-useoncall for details.

GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
../../media/gpu/h264_decoder_unittest.cc:196:
    Function call: OutputPicture(0x7d8515807680)
          Returns: true
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/main/docs/gmock_cook_book.md#knowing-when-to-expect-useoncall for details.

[POC] H264Decoder forwarded first_mb_in_slice=65535 to accelerator->SubmitSlice() for a 300-macroblock picture (legal max 299). On VA-API this becomes VASliceParameterBufferH264.first_mb_in_slice and is used by the GPU driver as a write offset into the decode surface.

[       OK ] H264DecoderTest.UnvalidatedFirstMbInSliceReachesAccelerator (0 ms)
[----------] 1 test from H264DecoderTest (19 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (20 ms total)
[  PASSED  ] 1 test.
[1/1] H264DecoderTest.UnvalidatedFirstMbInSliceReachesAccelerator (0 ms)
SUCCESS: all tests passed.
Tests took 0 seconds.