Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tests] assertLog before act in ReactErrorBoundaries #28761

Merged
merged 1 commit into from
Apr 10, 2024

Conversation

rickhanlonii
Copy link
Member

Fixes tests blocking #28737

@react-sizebot
Copy link

Comparing: a5aedd1...77cab71

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 = 169.31 kB 169.31 kB = 52.76 kB 52.76 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js = 171.13 kB 171.13 kB = 53.33 kB 53.33 kB
facebook-www/ReactDOM-prod.classic.js = 588.80 kB 588.80 kB = 103.63 kB 103.63 kB
facebook-www/ReactDOM-prod.modern.js = 565.82 kB 565.82 kB = 99.54 kB 99.54 kB
test_utils/ReactAllWarnings.js Deleted 64.21 kB 0.00 kB Deleted 16.02 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 64.21 kB 0.00 kB Deleted 16.02 kB 0.00 kB

Generated by 🚫 dangerJS against 77cab71

@eps1lon
Copy link
Collaborator

eps1lon commented Apr 5, 2024

Why do we sometimes clear instead of asserting on logs?

@rickhanlonii
Copy link
Member Author

@eps1lon for these test, many of the tests in this file are already clearing, and I think it's because the log is huge, like 20+ or more lines in many cases. We should probably re-write these to clean up the logs instead of logging everything always for all tests, but I don't have time for a full refactor.

@rickhanlonii rickhanlonii merged commit b02199d into facebook:main Apr 10, 2024
38 checks passed
rickhanlonii added a commit that referenced this pull request Apr 10, 2024
We should force `assertLog` to be called before each `act` block to
ensure the queue is empty.

Requires fixing tests:
- #28745
- #28758
- #28759
- #28760
- #28761
- #28762
- #28763
- #28812
rickhanlonii added a commit that referenced this pull request Apr 11, 2024
rickhanlonii added a commit that referenced this pull request Apr 11, 2024
We should force `assertLog` to be called before each `act` block to
ensure the queue is empty.

Requires fixing tests:
- #28745
- #28758
- #28759
- #28760
- #28761
- #28762
- #28763
- #28812
rickhanlonii added a commit that referenced this pull request Apr 11, 2024
rickhanlonii added a commit that referenced this pull request Apr 11, 2024
We should force `assertLog` to be called before each `act` block to
ensure the queue is empty.

Requires fixing tests:
- #28745
- #28758
- #28759
- #28760
- #28761
- #28762
- #28763
- #28812
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
We should force `assertLog` to be called before each `act` block to
ensure the queue is empty.

Requires fixing tests:
- facebook#28745
- facebook#28758
- facebook#28759
- facebook#28760
- facebook#28761
- facebook#28762
- facebook#28763
- facebook#28812
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants