Skip to content

Rename devicelab catalina tests#94980

Merged
fluttergithubbot merged 2 commits intoflutter:masterfrom
keyonghan:rename_catalina
Dec 10, 2021
Merged

Rename devicelab catalina tests#94980
fluttergithubbot merged 2 commits intoflutter:masterfrom
keyonghan:rename_catalina

Conversation

@keyonghan
Copy link
Contributor

This PR renames:

  1. smoke_catalina_hot_mode_dev_cycle_ios__benchmark => hot_mode_dev_cycle_ios__benchmark
  2. smoke_catalina_start_up => flutter_gallery_mac__start_up (we already have one test flutter_gallery__start_up for linux/android).

This is a one time for all change on the test names, but it will affect the benchmark data which depends on test names.

#73907

@flutter-dashboard flutter-dashboard bot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Dec 9, 2021
@keyonghan
Copy link
Contributor Author

/cc @zanderso as this will affect the benchmark data.

scheduler: luci

- name: Mac_android smoke_catalina_start_up
- name: Mac_android flutter_gallery_mac__start_up
Copy link
Contributor

Choose a reason for hiding this comment

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

Based on https://github.com/flutter/flutter/wiki/Adding-a-new-Test-Shard#steps-to-add-a-new-framework-test-shard, should we be duplicating these with bringup: true to let the name soak in?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Based on the above doc, shall we update the framework_config.star specifically, or simply update .ci.yaml with bringup:true to wait for the roll?

Copy link
Contributor

Choose a reason for hiding this comment

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

Good point :-)

Can you update the docs, and mention that renaming a target that is postsubmit only doesn't require following the bringup process?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will update in a separate PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

Thanks, LGTM!

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

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants