It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

Here's a standalone test to reproduce the bug and verify that it's fixed:

testWidgets('semantics with attributed value should not fail',
    (tester) async {
  await tester.pumpWidget(
    MaterialApp(
      home: Semantics(
        attributedValue: AttributedString('test value'),
        child: const Placeholder(),
      ),
    ),
  );
});

@justinmc done ✅
Not sure what is up with that failing Linux build_tests_2_5 job. It fails while downloading Gradle 🤷‍♂️ Do you have any idea?

Absolutely no clue why these 2 jobs failed, any ideas @gnprice @justinmc ?

One failure is:

tree-status — Tree is currently broken. Please do not merge this PR unless it contains a fix for the tree.

So that means there's a problem unrelated to this PR. There's a few more words on "tree status" here:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#introduction

That one will automatically go green when the tree gets fixed, so there's nothing you need to do.

The other is Google testing. More about that here:
https://github.com/flutter/flutter/blob/master/docs/infra/Understanding-Google-Testing.md

You'll need a Google employee to investigate that one — so that means @justinmc :-)

thanks for the clarification. The tree status job is green again. @justinmc can you check on the "Google testing" job? Or can I do anything there?

Looks like the Google test failure was a timeout? Hopefully just that. I've rerun it.