Fix log assertion in cancels tasks in Scheduler-test

[sweetliquid]

Summary

In old tests, it was always pass the test even if the task was not cancelled. Because no fireMessageEvent was called and the onmessage was not executed.

[react-sizebot]

Comparing: a870b2d...527d3a9

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js	=	176.83 kB	176.83 kB	=	54.91 kB	54.91 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js	=	173.55 kB	173.55 kB	=	54.11 kB	54.11 kB
facebook-www/ReactDOM-prod.classic.js	=	594.16 kB	594.16 kB	=	104.42 kB	104.42 kB
facebook-www/ReactDOM-prod.modern.js	=	577.42 kB	577.42 kB	=	101.45 kB	101.45 kB
test_utils/ReactAllWarnings.js	Deleted	66.87 kB	0.00 kB	Deleted	16.36 kB	0.00 kB

Significant size changes

Includes any change greater than 0.2%:

Expand to show

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
test_utils/ReactAllWarnings.js	Deleted	66.87 kB	0.00 kB	Deleted	16.36 kB	0.00 kB

Generated by 🚫 dangerJS against 527d3a9

[eps1lon]

Nice catch. If we didn't cancel with the new test, it would fail with

● SchedulerBrowser › cancels tasks

    expect(received).toEqual(expected) // deep equality

    - Expected  - 0
    + Received  + 1

      Array [
        "Message Event",
    +   "Task",
      ]

      160 |       const actual = eventLog;
      161 |       eventLog = [];
    > 162 |       expect(actual).toEqual(expected);
          |                      ^
      163 |     }
      164 |     return {
      165 |       advanceTime,

Previously, it would have passed with and without the cancel.