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

[BEAM-1796] Make testShiftTimestampInvalid NeedsRunner instead of ROS #2305

Closed
wants to merge 1 commit into from

Conversation

tgroh
Copy link
Member

@tgroh tgroh commented Mar 23, 2017

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

  • Make sure the PR title is formatted like:
    [BEAM-<Jira issue #>] Description of pull request
  • Make sure tests pass via mvn clean verify. (Even better, enable
    Travis-CI on your fork and ensure the whole test matrix passes).
  • Replace <Jira issue #> in the title with the actual Jira issue
    number, if there is one.
  • If this contribution is large, please file an Apache
    Individual Contributor License Agreement.

Currently broken in Apex. I'm investigating.

@jkff @tweise

@tgroh
Copy link
Member Author

tgroh commented Mar 23, 2017

@tgroh
Copy link
Member Author

tgroh commented Mar 23, 2017

Run Apex RunnableOnService

@jkff
Copy link
Contributor

jkff commented Mar 23, 2017

Can you clarify what effect you're intending to achieve by changing it from ROS to NR?

@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.159% when pulling 109a5ba on tgroh:apex-shift-timestamp-invalid into ddc7595 on apache:master.

@asfbot
Copy link

asfbot commented Mar 23, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/8728/
--none--

@tgroh
Copy link
Member Author

tgroh commented Mar 23, 2017

Changing to RunnableOnService will cause it to not be picked up by the Apex RunnableOnService execution. That will stop it from breaking in Apex until the actual fix goes in.

@tgroh
Copy link
Member Author

tgroh commented Mar 23, 2017

Specifically, the Apex RunnableOnService category will not execute any NeedsRunner tests, as it's not configured to pick them up; the test needs to be marked as NeedsRunner or ignored as the SDK doesn't have the proper classes to execute the test in the right context (with a Pipeline Runner)

@jkff
Copy link
Contributor

jkff commented Mar 23, 2017

LGTM modulo Apex ROS tests passing. Please also file a JIRA about this breakage and tag the PR with it.

@asfbot
Copy link

asfbot commented Mar 23, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/845/
--none--

@tgroh tgroh changed the title Make testShiftTimestampInvalid NeedsRunner instead of ROS [BEAM-1796]Make testShiftTimestampInvalid NeedsRunner instead of ROS Mar 23, 2017
@tgroh tgroh changed the title [BEAM-1796]Make testShiftTimestampInvalid NeedsRunner instead of ROS [BEAM-1796] Make testShiftTimestampInvalid NeedsRunner instead of ROS Mar 23, 2017
@tgroh
Copy link
Member Author

tgroh commented Mar 23, 2017

@asfgit asfgit closed this in 47ba7b0 Mar 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants