Skip to content
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

Exclude instrumentation tests from generic build patterns #3707

Merged
merged 1 commit into from
Aug 19, 2021

Conversation

BenHenning
Copy link
Sponsor Member

@BenHenning BenHenning commented Aug 19, 2021

Explanation

This change automatically excludes all instrumentation tests from generic patterns like bazel build //... since instrumentation tests don't build correctly yet.

Reference Bazel documentation for the manual tag: https://docs.bazel.build/versions/main/guide.html#specifying-targets-to-build.

Checklist

  • The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
  • The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
  • The PR follows the style guide.
  • The PR does not contain any unnecessary auto-generated code from Android Studio.
  • The PR is made from a branch that's not called "develop".
  • The PR is made from a branch that is up-to-date with "develop".
  • The PR's branch is based on "develop" and not on any other branch.
  • The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

@BenHenning BenHenning changed the title Update oppia_instrumentation_test.bzl Exclude instrumentation tests from generic build patterns Aug 19, 2021
native.android_instrumentation_test(
name = name,
target_device = "@android_test_support//tools/android/emulated_devices/generic_phone:android_23_x86_qemu2",
test_app = ":%sBinary" % name,
tags = ["manual"],
Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, I was wondering how to ignore test targets and this was exactly what I was looking for

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

I didn't think about there being a tag until today; we probably can revert the ComputeAffectedTests bits but eh.

Copy link
Contributor

@FareesHussain FareesHussain left a comment

Choose a reason for hiding this comment

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

LGTM, thanks

@FareesHussain FareesHussain removed their assignment Aug 19, 2021
@oppiabot oppiabot bot added the PR: LGTM label Aug 19, 2021
@oppiabot
Copy link

oppiabot bot commented Aug 19, 2021

Hi @BenHenning, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to merge this PR once the CI checks pass and you're happy with it. Thanks!

@BenHenning
Copy link
Sponsor Member Author

Thanks! Enabling auto-merge.

@BenHenning BenHenning enabled auto-merge (squash) August 19, 2021 21:15
@BenHenning BenHenning merged commit 3340d7c into develop Aug 19, 2021
@BenHenning BenHenning deleted the automatically-exclude-all-instrumentation-tests branch August 19, 2021 21:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants