[webcrypto] Remove the MAYBE() test macro

[webcrypto] Remove the MAYBE() test macro

Now that all of the tests run on both BoringSSL and NSS, there is no need for the MAYBE() macro.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=287301

[eroman, 2014-07-30 04:27:12]

(There are 3 CL which have to land sequentially before this one can)

https://codereview.chromium.org/430733002/diff/1/content/child/webcrypto/shar...
File content/child/webcrypto/shared_crypto_unittest.cc (right):

https://codereview.chromium.org/430733002/diff/1/content/child/webcrypto/shar...
content/child/webcrypto/shared_crypto_unittest.cc:1022: TEST_F(SharedCryptoTest,
AesCbcSampleSets) {
Some of these clearly should have been enabled earlier, but I missed them when
turning on individual features.

[eroman, 2014-07-30 15:57:16]

Actually I am going to re-work this CL:

  * Will TBR a CL which enables the tests which already pass, and has no
dependencies on other changelists landing

  * Will incorporate the missing AES-KW test into that unsubmitted changelist

   * This changelist will then become pure about removing the MAYBE() macro

(Opted for this approach since I want to get the tests running ASAP before I
leave on vacation, and the dependent CLs may not land in time)

[eroman, 2014-07-30 18:13:36]

ready for review again now.

[Ryan Sleevi, 2014-07-30 18:16:31]

lgtm

[eroman, 2014-08-03 16:27:56]

The CQ bit was checked by eroman@chromium.org

[commit-bot: I haz the power, 2014-08-03 16:28:33]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/eroman@chromium.org/430733002/40001

[commit-bot: I haz the power, 2014-08-03 17:12:19]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_clang_dbg on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
  android_dbg on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg/bui...)
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_compile_dbg on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel/...)
  win8_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)
  win_chromium_compile_dbg on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
  win_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel/...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-03 17:16:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-03 17:16:03]

Try jobs failed on following builders:
  mac_chromium_compile_dbg on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[eroman, 2014-08-04 04:03:13]

The CQ bit was checked by eroman@chromium.org

[commit-bot: I haz the power, 2014-08-04 04:04:17]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/eroman@chromium.org/430733002/60001

[commit-bot: I haz the power, 2014-08-04 06:00:56]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-04 08:03:21]

Change committed as 287301