Skip to content

build: do not consider e2e test targets as flaky locally #20371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 28, 2020

Conversation

devversion
Copy link
Member

Running e2e test targets locally means that Bazel will re-run
them a second time if they fail. This slows-down local development
as there is no way to see the test failure before Bazel completed
the second run. We should not consider e2e tests as flaky locally.

Developers could re-run the test themselves if they see it being
flaky. Also flaky e2e tests only seem to happen if lots of e2e
tests execute concurrently. This is not often the case locally.

Running e2e test targets locally means that Bazel will re-run
them a second time if they fail. This slows-down local development
as there is no way to see the test failure before Bazel completed
the second run. We should not consider e2e tests as flaky locally.

Developers could re-run the test themselves if they see it being
flaky. Also flaky e2e tests only seem to happen if lots of e2e
tests execute concurrently. This is not often the case locally.
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Aug 20, 2020
@devversion devversion requested a review from a team as a code owner August 20, 2020 13:28
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 20, 2020
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Aug 21, 2020
@jelbourn jelbourn merged commit fd34f35 into angular:master Aug 28, 2020
jelbourn pushed a commit that referenced this pull request Aug 28, 2020
Running e2e test targets locally means that Bazel will re-run
them a second time if they fail. This slows-down local development
as there is no way to see the test failure before Bazel completed
the second run. We should not consider e2e tests as flaky locally.

Developers could re-run the test themselves if they see it being
flaky. Also flaky e2e tests only seem to happen if lots of e2e
tests execute concurrently. This is not often the case locally.

(cherry picked from commit fd34f35)
annieyw pushed a commit to annieyw/components that referenced this pull request Aug 31, 2020
Running e2e test targets locally means that Bazel will re-run
them a second time if they fail. This slows-down local development
as there is no way to see the test failure before Bazel completed
the second run. We should not consider e2e tests as flaky locally.

Developers could re-run the test themselves if they see it being
flaky. Also flaky e2e tests only seem to happen if lots of e2e
tests execute concurrently. This is not often the case locally.
mmalerba pushed a commit that referenced this pull request Sep 2, 2020
Running e2e test targets locally means that Bazel will re-run
them a second time if they fail. This slows-down local development
as there is no way to see the test failure before Bazel completed
the second run. We should not consider e2e tests as flaky locally.

Developers could re-run the test themselves if they see it being
flaky. Also flaky e2e tests only seem to happen if lots of e2e
tests execute concurrently. This is not often the case locally.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants