Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFlaky `test_aio` CircleCI job due to size check #37699
Open
Milestone
Comments
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 24, 2020
…flakes As reported in angular#37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected.
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 24, 2020
…flakes As reported in angular#37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected.
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 24, 2020
…flakes As reported in angular#37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected.
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 24, 2020
…flakes As reported in angular#37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected.
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 24, 2020
…flakes As reported in angular#37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected.
|
FYI, I created #37703 to capture more info to help debug this (the next time it happens). |
|
another instance: #37686 (comment) |
AndrewKushnir
added a commit
that referenced
this issue
Jun 26, 2020
…flakes (#37703) As reported in #37699, the size of the main angular.io bundle sometimes ends up bigger than expected on CI. This usually goes away after rerunning the job a couple of times. It is unclear what is causing this. In order to help debug the issue, this commit stores the JS files that are checked as part of the aio payload-size check as CI artifacts, where they can be retrieved from and inspected. PR Close #37703
|
two jobs within the same workflow affected by the problem: And as a bonus - within the same workflow we had the following failures that I cannot reproduce locally:
|
@IgorMinar FYI these two additional issues were resolved in 98c047b (in master) and 78460c1 (in patch). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
test_aioCircleCI job sometimes fails false-positively with the payload size error (over 20kb diff):Example of the most recent failure in master can be found here. In that particular case, it was a docs-only commit.
Restarting the CircleCI job usually fixes the problem.
cc @gkalpak