-
Notifications
You must be signed in to change notification settings - Fork 6k
running web tests only on DEPS and web directories #21613
Conversation
keyonghan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Leave approval to @yjbanov .
yjbanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
I rerun the failing tests: https://ci.chromium.org/p/flutter/builders/try/Linux%20Web%20Framework%20tests/316 Btw these tests are not related to the PR since this is a configuration PR (not related to engine/framework code) |
tests passed. |
flutter/engine@7e6191d...9a7b556 2020-10-06 [email protected] hasStrings Linux (flutter/engine#21388) 2020-10-06 [email protected] add api_conform_test to analyze step. remove build script. (flutter/engine#21633) 2020-10-06 [email protected] Roll Fuchsia Mac SDK from 8q-OCkyhO... to xM2vYLfIT... (flutter/engine#21635) 2020-10-06 [email protected] Roll Skia from 33b42e12ab71 to 107114dd1d6e (5 revisions) (flutter/engine#21634) 2020-10-06 [email protected] Roll Fuchsia Linux SDK from HeAkKHbFY... to kr1tNtZvZ... (flutter/engine#21630) 2020-10-06 [email protected] running web tests only on DEPS and web directories (flutter/engine#21613) 2020-10-06 [email protected] Roll Skia from c3bdd1c597dc to 33b42e12ab71 (6 revisions) (flutter/engine#21628) 2020-10-06 [email protected] Use the gpu config for shell_unittests to declare SHELL_ENABLE_{GL,VULKAN} (flutter/engine#21603) 2020-10-06 [email protected] [linux] Allow engine flags via environment vars (flutter/engine#21497)
* running web tests only on DEPS and web directories * adding more folders to skip tests

I suggest we run the web tests only on certain directories.
Today, Linux Web Builders were very busy and it was hard to do test_harness development. Unless we have other reasons to run tests on all changes, I believe it's better to keep our list small as we did in cirrus.