Skip to content

Conversation

@godofredoc
Copy link
Contributor

These tests are blocking rolls of the recipe dependencies.

https://ci.chromium.org/p/flutter/builders/try/recipes-with-led/b8800032390708370785?

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@godofredoc godofredoc requested a review from keyonghan as a code owner October 17, 2022 20:42
@godofredoc godofredoc requested a review from jmagman October 17, 2022 20:42
@jmagman
Copy link
Member

jmagman commented Oct 17, 2022

An error occurred while installing ffi (1.15.5), and Bundler cannot continue.

Hm, why is this needed on master?

https://flutter-review.googlesource.com/c/recipes/+/34400/comments/3de8d3da_334648a4

recipes-with-led isn't configured to correctly run on release branches. It's testing against main configs, so release team unfortunately has to monitor in prod.

@godofredoc
Copy link
Contributor Author

An error occurred while installing ffi (1.15.5), and Bundler cannot continue.

Hm, why is this needed on master?

https://flutter-review.googlesource.com/c/recipes/+/34400/comments/3de8d3da_334648a4

recipes-with-led isn't configured to correctly run on release branches. It's testing against main configs, so release team unfortunately has to monitor in prod.

Mac_arm64 tool_host_cross_arch_tests is failing consistently and should not be blocking recipes CLs. Maybe we need a test that fails if we set bringup: true with enable_cq: true?

If Mac_x64 tool_host_cross_arch_tests should be blocking recipe CLs I can update this change to only remove CQ from the arm64 and try to find the error.

@jmagman
Copy link
Member

jmagman commented Oct 18, 2022

@godofredoc
Copy link
Contributor Author

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.

I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.

I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.

I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

There is something very strange with this test, led is not collecting $flutter/osx_sdk property. Can we land this change as it is and bring the tests to recipes cq once the test is fixed? They are failing in different fronts and they are blocking multiple fixes to recipes.

Copy link
Contributor

@ricardoamador ricardoamador left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@godofredoc
Copy link
Contributor Author

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.
I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.
I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

The arm recipe crash is #113231, which is why it has ignore_flakiness: "true" #112999.
I don't understand why x64 has an ffi error though, that should be passing: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/flutter-try-builder_chops-service-accounts.iam.gserviceaccount.com/aa5c8a8d8a5420b170861e817546b277f995f17b8c8e86d1ca9a44f5181fb7ab/+/build.proto

There is something very strange with this test, led is not collecting $flutter/osx_sdk property. Can we land this change as it is and bring the tests to recipes cq once the test is fixed? They are failing in different fronts and they are blocking multiple fixes to recipes.

Tracking issue: #113611

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants