You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that if the test does not fail (timeout) it takes around 20 minutes. The prepare and create flutter archive, the step that is failing takes ~17 minutes to complete.
In each case the step times out after the downloads when it is trying to prepare the tar ball. Not sure why that is taking so long.
OK I checked each of those links and in every single one the last step in the log is Running "tar cJf /b/s/w/ir/x/w/archive/flutter_linux_3.16.0-<SOME_VERSION>.pre-master.tar.xz flutter" in /b/s/w/ir/x/w/archive.
Does that tar step run on every build or is the result cached/shared in some way?
Nothing in the logs indicates anything else hanging for longer than I would expect and none of the errors appear related to android.
@ricardoamador feel free to unassign yourself. This was just my way of sending this back to infra but I never assigned the bug to myself as i was investigating.
Okay not sure if this is THE issue but I did notice that when the building of the archive is taking a long time causing the timeout it appears that there are other packages or directories that may have been left over from something else and not cleaned up properly. I took a look and compared the failing ones that time out they are adding a ton of other items when building the archive:
I did a quick comparison of the builds and what they are putting into the archive, and if you search for this string, "flutter/bin/cache/artifacts/," in both builds you will get about 220 items which looks to be the artifacts the test is expecting versus the failing build that shows 7,402 items all the way to the time limit, which includes fuchsia packages for different architectures which I am sure are not meant to be there.
So it looks like something is not cleaning up and leaving packages around that are getting picked up by this test and I need to figure out why this is.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
ricardoamador commentedon Nov 2, 2023
The last few are timeouts. Can you look to see why packaging is taking so long?
reidbaker commentedon Nov 3, 2023
in this infra flake I see 7.5 minutes of documented downloading
and some download tasks that do not have timestamps or durations. What is the timeout for this test or where can I look it up myself.
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3868/overview
reidbaker commentedon Nov 3, 2023
I will add that I see no error failures in the last 600 or so run only infra flakes for steps we know can be flakey like downloading.
ricardoamador commentedon Nov 3, 2023
Hi @reidbaker I usually check here for the historical runs: https://ci.chromium.org/ui/p/flutter/builders. It shows all our builders in all pools.
It appears that if the test does not fail (timeout) it takes around 20 minutes. The prepare and create flutter archive, the step that is failing takes ~17 minutes to complete.
In each case the step times out after the downloads when it is trying to prepare the tar ball. Not sure why that is taking so long.
reidbaker commentedon Nov 3, 2023
ricardoamador commentedon Nov 3, 2023
Sure, no problem. Here are the last few with the same error:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3884/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3868/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3844/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3820/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3817/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20flutter_packaging_test/3762/overview
reidbaker commentedon Nov 6, 2023
OK I checked each of those links and in every single one the last step in the log is
Running "tar cJf /b/s/w/ir/x/w/archive/flutter_linux_3.16.0-<SOME_VERSION>.pre-master.tar.xz flutter" in /b/s/w/ir/x/w/archive.Does that tar step run on every build or is the result cached/shared in some way?
Nothing in the logs indicates anything else hanging for longer than I would expect and none of the errors appear related to android.
reidbaker commentedon Nov 6, 2023
@ricardoamador feel free to unassign yourself. This was just my way of sending this back to infra but I never assigned the bug to myself as i was investigating.
ricardoamador commentedon Jan 3, 2024
@reidbaker circling back. No problem, we can leave it assigned as is.
ricardoamador commentedon Jan 3, 2024
cc @reidbaker
Okay not sure if this is THE issue but I did notice that when the building of the archive is taking a long time causing the timeout it appears that there are other packages or directories that may have been left over from something else and not cleaned up properly. I took a look and compared the failing ones that time out they are adding a ton of other items when building the archive:
For example here is a build that passed and is a relatively short amount of time around the average of 20 or so minutes: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8761139945712791889/+/u/prepare_and_create_a_flutter_archive/stdout
And here is one from a build that timed out:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8761169327645302481/+/u/prepare_and_create_a_flutter_archive/stdout
I did a quick comparison of the builds and what they are putting into the archive, and if you search for this string, "flutter/bin/cache/artifacts/," in both builds you will get about 220 items which looks to be the artifacts the test is expecting versus the failing build that shows 7,402 items all the way to the time limit, which includes fuchsia packages for different architectures which I am sure are not meant to be there.
So it looks like something is not cleaning up and leaving packages around that are getting picked up by this test and I need to figure out why this is.
CaseyHillers commentedon Jan 3, 2024
@ricardoamador is this a dupe of #139597?
ricardoamador commentedon Jan 3, 2024
Closing as a result of the fix made in the issue @CaseyHillers linked.
github-actions commentedon Jan 17, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.