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
Fix for reporting correct bundle size #11544
Fix for reporting correct bundle size #11544
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks reasonable - will be interested to see it run against this PR :)
bundle size not reported :( |
Might be due to that other bug we were observing, that it only successfully reports bundle size if the first run succeeds. Maybe try opening a fresh PR with this change and see if you can get a clean run? |
|
Can we write some description for the PR? Not all people have access to azure work item |
I think there is some heuristic to not report to GH if there is no difference |
|
For this PR, there was no difference in bundle size -- For one of the PR against which the bundle size was not reported: #11491 -- the logs are as follows:
Backup baseline commit is looked up when baseline build is undefined or successful baseline build does not have the needed build artifacts. Not sure why the baseline build is undefined in this case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit on a comment, but looks good!
|
This commit is queued for merging with the |
The bundle size comparison tool is currently comparing baseline against main branch. The baseline for pull requests opened against the next branch are incorrect. This pull request aims to fix the baseline comparison by setting an env variable
TARGET_BRANCH_NAMEas branch that is the target of a pull request. By default, the env variable is set tomain.AB#1570