[null-safety] remove all usage of --enable-experiment from CI #69841

Activity

1. jonahwilliams

   added

   a: null-safetySupport for Dart's null safety featureSupport for Dart's null safety feature

   P2Important issues not at the top of the work listImportant issues not at the top of the work list

   on Nov 5, 2020
2. pedromassangocode

   added

   passed first triage

   on Nov 5, 2020
3. kf6gpe

   added

   toolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.

   team-infraOwned by Infrastructure teamOwned by Infrastructure team

   and removed

   toolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.

   on Feb 8, 2021
4. godofredoc

   added

   passed secondary triage

   on Feb 11, 2021
5. godofredoc

   assigned

   CaseyHillers

   on Feb 11, 2021
6. CaseyHillers commented on Feb 12, 2021

   

   CaseyHillers

   on Feb 12, 2021

   Contributor

   More actions

   There's still 22 instances of this flag across Flutter - https://cs.opensource.google/search?q=%22--enable-experiment%22&ss=flutter&start=1

   @jonahwilliams is this flag safe to remove now?
7. jonahwilliams commented on Feb 12, 2021

   

   jonahwilliams

   on Feb 12, 2021

   ContributorAuthor

   More actions

   Unit tests that are passing this flag are fine, since they're most likely just validating that it can be passed. Anything that is doing integration level testing should make sure that it keeps working without the flag.
8. CaseyHillers

   removed their assignment

   on Mar 7, 2022
9. jonahwilliams commented on Feb 14, 2023

   

   jonahwilliams

   on Feb 14, 2023

   ContributorAuthor

   More actions

   I believe all of this work has been done
10. jonahwilliams

    closed this as completedon Feb 14, 2023
11. github-actions commented on Mar 3, 2023

    

    github-actionsbot

    on Mar 3, 2023

    More actions

    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.
12. github-actions

    locked as resolved and limited conversation to collaborators on Mar 3, 2023