[
https://issues.apache.org/jira/browse/BEAM-6009?focusedWorklogId=168373&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-168373
]
ASF GitHub Bot logged work on BEAM-6009:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Nov/18 16:50
Start Date: 21/Nov/18 16:50
Worklog Time Spent: 10m
Work Description: swegner commented on issue #7077: [BEAM-6009] gradle
config for batch+streaming portable flink vr tests
URL: https://github.com/apache/beam/pull/7077#issuecomment-440735597
> so it seems unrelated, but I'd appreciate another set of eyes on it.
thanks!
Yes, I believe your analysis is correct. Here's my understanding of things:
1. SeedJob produces new Jenkins job definitions by running the job dsl
scripts
1. The new job definitions are committed at the end of the SeedJob run iff
it succeeded.
1. All jobs started after the end of the SeedJob execution will use the new
job definitions
1. A subsequent SeedJob run will overwrite existing jobs at the end of its
successful completion.
Based on the timings you list above, your `Flink PortableValidatesRunner
Batch` should have used your job definitions. I'll note that [SeedJob run
#3028](https://builds.apache.org/job/beam_SeedJob/3028/) wasn't actually
triggered from my PR; it was run automatically from master based on the cron
schedule. You can see this from the Jenkins job page:
> Started by timer
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 168373)
Time Spent: 3h 40m (was: 3.5h)
> PortableValidatesRunner runs only in batch mode
> -----------------------------------------------
>
> Key: BEAM-6009
> URL: https://issues.apache.org/jira/browse/BEAM-6009
> Project: Beam
> Issue Type: Test
> Components: build-system, testing
> Reporter: Maximilian Michels
> Priority: Major
> Labels: portability, portability-flink
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The PortableValidatesRunner tasks, e.g.
> {{:beam-runners-flink_2.11-job-server:validatesPortableRunner}} only runs in
> batch mode. Similar to the Python PortableValidatesRunner tests
> ({{:beam-sdks-python:flinkValidatesRunner}}, the test suite should also run
> with the {{--streaming}} flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
