I made a number of changes to the CiBot over the weekend.
- '@flinkbot run azure' previously triggered an entirely new build based
on the last completed one. It now instead retries the last completed
build, only running the jobs that actually failed. It basically behaves
like the "Rerun failed
Hi Wu,
If you are using the FileSink, it would use a random UUID on startup, it would
be changed
after failover, thus the new records would be writes to files like
--.suffix.
And logically the sink in 1.14 should be able to recover from an existing
savepoint from previous version smoothly sin
Mahendran Ponnusamy created FLINK-24494:
---
Summary: Avro conluent Resigry SQL not fails to write to the topic
with schema with default value for int
Key: FLINK-24494
URL: https://issues.apache.org/jira/browse
Thanks for that great job, Chesnay! "Rerun failed jobs" will help a lot.
Best,
Yangze Guo
On Sun, Oct 10, 2021 at 4:56 PM Chesnay Schepler wrote:
>
> I made a number of changes to the CiBot over the weekend.
>
> - '@flinkbot run azure' previously triggered an entirely new build based
> on the la
Xintong Song created FLINK-24495:
Summary: Python installdeps hangs
Key: FLINK-24495
URL: https://issues.apache.org/jira/browse/FLINK-24495
Project: Flink
Issue Type: Bug
Components
Thanks! "only running the jobs that actually failed" is very useful.
A small problem may have been solved. After a commit, we cannot rerun
the failed test before the commit. (The test triggered by commit has
not finished yet. The test triggered again should run the full cases)
Best,
Jingsong
On
Hi Chesnay,
Thanks for the effort. It is a very useful improvement.
I have a minor question. Please forgive me if the question is too naive.
Since '@flinkbot run azure' now behaves like "Rerun failed jobs", is there
any way to trigger an entirely new build? Because some times I'm not sure
the passe
Thanks for the effort, @Chesnay. This is super helpful.
@Jing,
Every push to the PR branch should automatically trigger an entire new
build. `@flinkbot run azure` should only be used when you want to re-run
the failed stages without changing the PR. E.g., when running into known
unstable cases tha
Juha created FLINK-24496:
Summary: Querying job details in the REST API fails
Key: FLINK-24496
URL: https://issues.apache.org/jira/browse/FLINK-24496
Project: Flink
Issue Type: Bug
Compon
Juha created FLINK-24497:
Summary: Kafka metrics fetching throws IllegalStateException
Key: FLINK-24497
URL: https://issues.apache.org/jira/browse/FLINK-24497
Project: Flink
Issue Type: Bug
Dawid Wysakowicz created FLINK-24498:
Summary: KafkaShuffleITCase fails with "The topic metadata failed
to propagate to Kafka broker"
Key: FLINK-24498
URL: https://issues.apache.org/jira/browse/FLINK-24498
Nice! Thanks for the effort Chesnay, this is really a huge step forward!
Best,
D.
On Mon, Oct 11, 2021 at 6:02 AM Xintong Song wrote:
> Thanks for the effort, @Chesnay. This is super helpful.
>
> @Jing,
> Every push to the PR branch should automatically trigger an entire new
> build. `@flinkbot
Hi,
There's already a Jira ticket [1] for this but no one is yet working on it.
We'd welcome it if you would like to pick it up, I can assign it to you.
Best regards,
Martijn
[1] https://issues.apache.org/jira/browse/FLINK-19930
On Fri, 8 Oct 2021 at 16:12, Purushotham Pushpavanthar <
pushpava
13 matches
Mail list logo