Repro case with a master build: https://codesandbox.io/s/stoic-mcnulty-dhygf?file=/src/App.js:668-703

Expected: we see content after a second.
Actual: fallback never resolves.

This happens in a sequence of:

1. Normal update
   - which suspends
2. Idle update
   - which also suspends
3. An unrelated normal update immediately followed by a ping (so they're batched)
   - here, we decide to stay on fallback, but should've shown the content

If you remove `_setVersion(v => v + 1);` on line 44 then the issue goes away.
renderExpirationTime: ExpirationTime,
) {
  let context: ReactContext<any> = workInProgress.type;
   The logic below for Context differs depending on PROD or DEV mode. In
   DEV mode, we create a separate object for Context.Consumer that acts
   like a proxy to Context. This proxy object adds unnecessary code in PROD
   so we use the old behaviour (Context.Consumer references Context) to
   reduce size and overhead. The separate object references context via
   a property called "_context", which also gives us the ability to check
   in DEV mode if this property exists or not and warn if it does not.
  if (__DEV__) {
    if ((context: any)._context === undefined) {
       
       
       
      if (context !== context.Consumer) {
        if (!hasWarnedAboutUsingContextAsConsumer) {
          hasWarnedAboutUsingContextAsConsumer = true;
          console.error(
            'Rendering <Context> directly is not supported and will be removed in ' +
              'a future major release. Did you mean to render <Context.Consumer> instead?',
          );
        }
      }
    } else {
      context = (context: any)._context;
    }
  }
  const newProps = workInProgress.pendingProps;
  const render = newProps.children;