Hi all,
please know that this subject has come forward:The first PR
(https://github.com/apache/beam/pull/5464) writes perfs to
BQThe second one (https://github.com/apache/beam/pull/4976) runs the
PostCommits and configure the exports to BQFirst
PR needs to be merged before second one and once t
Hi all,
As discussed here I proposed a PR (https://github.com/apache/beam/pull/4976) to
schedule nexmark runs as post commit
tests. the post commits run
* NM on direct runner in batch mode
* NM on direct runner in streaming mode
* NM on flink runner in batch mode
* NM on flink runner in stream
Hi,
I would suggest to prepare a Maven profile to perform nexmark runs.
Then, I can setup a job (seed/manual) in Jenkins to run this.
Regards
JB
On 15/03/2018 22:13, Etienne Chauchot wrote:
So what next? Shall we schedule nexmark runs and add a Bigquery sink to
nexmark output?
Le lundi 1
So what next? Shall we schedule nexmark runs and add a Bigquery sink to nexmark
output?
Le lundi 12 mars 2018 à 10:30 +0100, Etienne Chauchot a écrit :
> Thanks everyone for your comments and support.
>
> Le vendredi 09 mars 2018 à 21:28 +, Alan Myrvold a écrit :
> > Great ideas. I want to se
Thanks everyone for your comments and support.
Le vendredi 09 mars 2018 à 21:28 +, Alan Myrvold a écrit :
> Great ideas. I want to see a daily signal for anything that could prevent a
> release from happening, and precommits
> that are fast and reliable for areas that are commonly broken by co
Le samedi 10 mars 2018 à 12:57 +0100, Łukasz Gajowy a écrit :
> > - Integration tests: AFAIK we only run the ones in examples module and only
> > on demand. What about running all the IT
> > (in
> > particular IO IT) as a cron job on a daily basis with direct runner? Please
> > note that it will
Hi JB,
Le samedi 10 mars 2018 à 06:59 +0100, Jean-Baptiste Onofré a écrit :
> Good ideas !
>
> Validates runner tests and Integration tests should be nightly executed.
>
> For the Performance tests, it's a great idea, but not sure daily basis
> is required. Maybe two times per week ? As these te
Le vendredi 09 mars 2018 à 20:57 +, Kenneth Knowles a écrit :
> On Fri, Mar 9, 2018 at 3:08 AM Etienne Chauchot wrote:
> > Hi guys,
> >
> > I was looking at the various jenkins jobs and I wanted to submit a
> > proposition:
> >
> > - Validates runner tests: currently run at PostCommit for a
>
> - Integration tests: AFAIK we only run the ones in examples module and
> only on demand. What about running all the IT (in
> particular IO IT) as a cron job on a daily basis with direct runner?
> Please note that it will require some always up
> backend infrastructure.
>
Running IOITs on Direc
Good ideas !
Validates runner tests and Integration tests should be nightly executed.
For the Performance tests, it's a great idea, but not sure daily basis
is required. Maybe two times per week ? As these tests could be long, we
should avoid to block executors that could impact our PR build a
Great ideas. I want to see a daily signal for anything that could prevent a
release from happening, and precommits that are fast and reliable for areas
that are commonly broken by code changes.
We are now running the java quickstarts daily on a cron schedule, using
direct, dataflow, and local spar
On Fri, Mar 9, 2018 at 3:08 AM Etienne Chauchot
wrote:
> Hi guys,
>
> I was looking at the various jenkins jobs and I wanted to submit a
> proposition:
>
> - Validates runner tests: currently run at PostCommit for all the runners.
> I think it is the quickest way to see
> regressions. So keep it
Hi guys,
I was looking at the various jenkins jobs and I wanted to submit a proposition:
- Validates runner tests: currently run at PostCommit for all the runners. I
think it is the quickest way to see
regressions. So keep it that way
- Integration tests: AFAIK we only run the ones in examples
13 matches
Mail list logo
