These two tests create duplicate TestProfiles for a single BrowserContext. Normally, the Profile *is* the BrowserContext, so this creates a weird situation.  Generally, a BrowserContextKeyedService is used for only one Profile, which has a single StoragePartition.

However, in these two tests, BrowserContextKeyedServices are shared by both Profiles (Since they have the same BrowserContext), but each profile also has its own StoragePartition.

I'm working on separating out the network code (ProfileIOData) from being attached to the Profile to being attached to the StoragePartition, but I'm also using a BrowserContextKeyedService to hold onto objects Chrome-side.  One service with two Profiles doesn't work very well.

I've been trying to switch the tests over to use TestingProfile::BuildIncognito() - that does fixes the crashes the tests run into with my CL, but it makes the tests fail.  :(