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
{{ message }}
Repository navigation
Linux flutter_packaging_test intermittently timing out #139597
Also note, that when this test passes, it completes in ~20 minutes. From the logs I see nothing obvious, although this test writes a lot to disk and uses a lot of network traffic.
Looking at the last few infra failures, they seem to all be flaking when packaging the Fuchsia artifacts.
I don't know why Fuchsia's being pulled in, and that seems like something we can remove. When I run flutter precache locally on linux, I'm not pulling in a Fuchsia artifacts. I'll take a look into removing the Fuchsia artifacts from the packaging builds.
Verified the issue is when we download Fuchsia artifacts (like FEMU). The bots in a bad state as a previous test ran that configured the Flutter tool to checkout Fuchsia artifacts.
Monitoring the past ~24 hours of builds doesn't show this issue anymore, however, it's only like ~15 builds. I'll leave this bug open and will check back in after the new year to see if there's any more work here.
Monitoring the past ~24 hours of builds doesn't show this issue anymore, however, it's only like ~15 builds. I'll leave this bug open and will check back in after the new year to see if there's any more work here.
Sounds like a plan, thanks for the (probably) fix!
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
keyonghan commentedon Dec 5, 2023
/cc @CaseyHillers This is the issue we just talked about.
[ci.yaml] Add runif filters and stricter timeout to packaging_test (#…
make the tar c command in prepare_package.dart verbose (#139687)
CaseyHillers commentedon Dec 19, 2023
Looking at the last few infra failures, they seem to all be flaking when packaging the Fuchsia artifacts.
I don't know why Fuchsia's being pulled in, and that seems like something we can remove. When I run
flutter precachelocally on linux, I'm not pulling in a Fuchsia artifacts. I'll take a look into removing the Fuchsia artifacts from the packaging builds.CaseyHillers commentedon Dec 19, 2023
Verified the issue is when we download Fuchsia artifacts (like FEMU). The bots in a bad state as a previous test ran that configured the Flutter tool to checkout Fuchsia artifacts.
CaseyHillers commentedon Dec 19, 2023
I sent https://flutter-review.googlesource.com/c/recipes/+/53281 with a proposed fix that will run
flutter config --clear-featureswhenever setting up new Flutter environments on CI.CaseyHillers commentedon Dec 21, 2023
Monitoring the past ~24 hours of builds doesn't show this issue anymore, however, it's only like ~15 builds. I'll leave this bug open and will check back in after the new year to see if there's any more work here.
christopherfujino commentedon Dec 21, 2023
Sounds like a plan, thanks for the (probably) fix!
ricardoamador commentedon Jan 3, 2024
@CaseyHillers can you look into this: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20android%20views/41430/overview
I just noticed this failure when looking into something else.
CaseyHillers commentedon Jan 3, 2024
Looking at https://github.com/flutter/flutter/pull/140795/checks, that appears to be an expected failure with that PR. In the future, I recommend looking at prod failures to avoid the noise.
ricardoamador commentedon Jan 3, 2024
Got it. Yeah no worries then.
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.