Mac benchmark tests are running on different spec bots #119780

Activity

1. jmagman

   added

   c: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.

   platform-macosBuilding on or for macOS specificallyBuilding on or for macOS specifically

   on Feb 2, 2023
2. jmagman commented on Feb 2, 2023

   

   jmagman

   on Feb 2, 2023

   MemberAuthor

   More actions

   I think this was a problem before #119762 since even within our Intel bot pool we were running host benchmark tests (like macOS tests) on different Mac models.
3. jmagman

   added

   P1

   P1High-priority issues at the top of the work listHigh-priority issues at the top of the work list

   and removed

   P1

   on Feb 2, 2023
4. jmagman

   self-assigned this

   on Feb 2, 2023
5. jmagman

   added

   team-infraOwned by Infrastructure teamOwned by Infrastructure team

   on Feb 2, 2023
6. jmagman commented on Feb 2, 2023

   

   jmagman

   on Feb 2, 2023

   MemberAuthor

   More actions

   I reverted #119762 with #119784 but we should still investigate if there are any macOS benchmark issues with differences in the Intel bots
7. jmagman

   removed their assignment

   on Feb 2, 2023
8. jmagman

   added

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

   team: benchmarkPerformance issues found by inspecting benchmarksPerformance issues found by inspecting benchmarks

   and removed

   P1High-priority issues at the top of the work listHigh-priority issues at the top of the work list

   on Feb 2, 2023
9. auto-submit

   closed this as completedin #119871on Feb 3, 2023
10. 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.
11. github-actions

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