<!--
  Note: if the issue is about documentation or the website, please file it at:
  https://github.com/reactjs/reactjs.org/issues/new
-->

**Do you want to request a *feature* or report a *bug*?**
bug, I believe, unless I misunderstand how it works
**What is the current behavior?**
Given a `Suspense` inside `Suspense` case like
```
<Suspense fallback="Fallback 1">
  <LazyText1 text="First text" />
  <Suspense fallback="Fallback 2">
    <LazyText2 text="Second text!" />
  </Suspense>
</Suspense>
```

Promises in `LazyTexts` start resolving at the same time, but if `LazyText2` is resolved first it never renders, `Fallback 2` stays.

Result:
```
First text

Fallback 2
```

Please see https://codesandbox.io/s/234o4zry7n

**What is the expected behavior?**

Every `LazyText` displayed in the end
```
First text

Second text!
```

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
react, react-dom 16.6.0

expect(onInteractionScheduledWorkCompleted).toHaveBeenCalledTimes(2);
      expect(
        onInteractionScheduledWorkCompleted,
      ).toHaveBeenLastNotifiedOfInteraction(interactionLowPri);
      expect(getWorkForReactThreads(onWorkStarted)).toHaveLength(3);
      expect(getWorkForReactThreads(onWorkStopped)).toHaveLength(2);
    });
    it('should trace work spawned by a commit phase lifecycle and setState callback', () => {
      let instance;
      class Example extends React.Component {
        state = {
          count: 0,
        };
        componentDidMount() {
          advanceTimeBy(10); 
          this.setState({count: 1}); 
        }
        componentDidUpdate(prevProps, prevState) {
          if (this.state.count === 2 && prevState.count === 1) {
            advanceTimeBy(10); 
            this.setState({count: 3}); 
          }
        }
        render() {
          instance = this;
          ReactTestRenderer.unstable_yield('Example:' + this.state.count);
          return null;
        }
      }
      const interactionOne = {