<<< text/html; charset=UTF-8: Unrecognized >>>
Is there somewhere we could document this?
On Thu, Sep 15, 2022 at 6:45 AM Moritz Mack wrote:
> Thank you, Andrew!
>
> Exactly what I was looking for, that’s awesome!
>
>
>
> On 15.09.22, 06:37, "Alexey Romanenko" wrote:
>
>
>
>
>
> Ahh, great! I didn’t know that 'beam-perf’ label is used for
I agree with Austin on this one, it makes sense to be realistic, but I'm
concerned about just blanket reducing the priority on all flakes. Two
classes of issues that could certainly be dropped to P2:
- Issues tracking flakes that have not been sickbayed yet (e.g.
Thank you, Andrew!
Exactly what I was looking for, that’s awesome!
On 15.09.22, 06:37, "Alexey Romanenko" wrote:
Ahh, great! I didn’t know that 'beam-perf’ label is used for that.
Thanks!
> On 14 Sep 2022, at 17:47, Andrew Pilloud wrote:
>
> We do have a dedicated machine for benchmarks. This
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/23227 [Bug]: Python SDK
