015383d1d7
There are no similar macros in gtest. They do recommend pulling another library (gmock) and use that, but having our own let us control the output more precisely. Extracted the code from a similar existing macro in blob_test.cpp, making changes to the output. A check like ASSERT_U8_ARRAY_EQUAL(expected_u8, result_u8, 32); that fails will output ``` Expected 32 values to be equal but found 1 that differ: expected_u8 values are: [000] 29 44 00 00 44 60 cb 80 93 65 07 c0 08 00 40 29 [016] 03 81 00 00 5c a0 21 87 *b0 31 00 00 00 00 00 60 result_u8 values are: [000] 29 44 00 00 44 60 cb 80 93 65 07 c0 08 00 40 29 [016] 03 81 00 00 5c a0 21 87 *af 31 00 00 00 00 00 60 ``` and a check like ASSERT_U64_ARRAY_EQUAL(expected_u64, result_u64, 4); ``` Expected 4 values to be equal but found 1 that differ: expected_u64 values are: [000] 80cb604400004429 29400008c0076593 [002] 8721a05c00008103 *60000000000031b0 result_u64 values are: [000] 80cb604400004429 29400008c0076593 [002] 8721a05c00008103 *60000000000031af ``` Note the asterisk indicating wrong values. The new header for extra macros is in src/gtest/include/ so it doesn't get in the way when updating the real gtest headers that are in src/gtest/include/gtest/. Reviewed-by: Dylan Baker <dylan@pnwbakers.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13672>
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.