Disable recovery test for USE_SYSTEM_SQLITE.

Disable recovery test for USE_SYSTEM_SQLITE.

Detact and short-circuit rather than using an #ifdef because the test
eventually needs to be adapted to actually test this case.  I'm just
not confident enough about possible edge cases to start deleting data.

BUG=299677
TBR=sky@chromium.org

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

[rohitrao (ping after 24h), 2013-09-27 19:49:30]

Test changes LGTM, thanks for fixing this!

Aside from unittests, the thumbnaildb code will probably still DCHECK if it ever
tries to load a corrupt database.

[Scott Hess - ex-Googler, 2013-09-27 19:52:19]

On 2013/09/27 19:49:30, rohitrao wrote:
> Aside from unittests, the thumbnaildb code will probably still DCHECK if it
ever
> tries to load a corrupt database.

That's a feature.  Real users don't run in debug builds, and developers usually
don't have corrupt databases, but developers often write code which throws
SQLite errors that they need to fix.  There is support for mocking things in a
test context.

[Scott Hess - ex-Googler, 2013-09-27 19:53:48]

I'm going to TBR to sky@, because I'm going OOT tomorrow and I don't want to
leave you hanging.

[Scott Hess - ex-Googler, 2013-09-27 19:54:55]

Oops, forgot to add Scott.

Scott, I'm TBR'ing this minor change to the thumnail database recovery test. 
This stuff isn't supported when USE_SYSTEM_SQLITE at this time.

[commit-bot: I haz the power, 2013-09-27 19:56:13]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shess@chromium.org/24989006/1

[commit-bot: I haz the power, 2013-09-27 22:07:22]

Retried try job too often on linux_chromeos for step(s) browser_tests,
unit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[Scott Hess - ex-Googler, 2013-09-27 22:09:17]

On 2013/09/27 22:07:22, I haz the power (commit-bot) wrote:
> Retried try job too often on linux_chromeos for step(s) browser_tests,
> unit_tests
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

Those do not look related.  Trying again.

[commit-bot: I haz the power, 2013-09-27 22:17:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shess@chromium.org/24989006/1

[commit-bot: I haz the power, 2013-09-27 23:42:34]

Retried try job too often on linux_chromeos for step(s) unit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[Scott Hess - ex-Googler, 2013-10-07 19:50:36]

On 2013/09/27 23:42:34, I haz the power (commit-bot) wrote:
> Retried try job too often on linux_chromeos for step(s) unit_tests
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

I still can't see why this is happening, so, rebase and hope.

[commit-bot: I haz the power, 2013-10-07 19:51:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shess@chromium.org/24989006/30001

[commit-bot: I haz the power, 2013-10-07 22:24:25]

Change committed as 227360