Hi all,
We have shut down most tests in the Jenkins Load Tests and Performance
Tests categories [1, 2], as they have been migrated to GitHub Actions for a
while and are continuously publishing the metrics as expected. Please refer
to https://github.com/apache/beam/pull/29092 for these tests. Note
Looks like for some reason the workflow didn't trigger. This is running on
GitHub's hosted runners, so my best guess is an outage.
Looking at a more refined query, this year there have been 14 issues that
were missed by the automation (3 had their milestone manually removed) -
Just grabbing one at random for an example,
https://github.com/apache/beam/issues/28635 seems like it was closed as
completed but not tagged.
I'm happy to see that the bot reads the version from the repo to find the
appropriate milestone, rather than using the nearest open one. Just
recording
On Tue, Oct 24, 2023 at 10:35 AM Kenneth Knowles wrote:
> Tangentially related:
>
> Long ago, attaching an issue to a release was a mandatory step as part of
> closing. Now I think it is not. Is it automatically happening? It looks
> like we have 820 with no milestone
>
Tangentially related:
Long ago, attaching an issue to a release was a mandatory step as part of
closing. Now I think it is not. Is it automatically happening? It looks
like we have 820 with no milestone
https://github.com/apache/beam/issues?q=is%3Aissue+no%3Amilestone+is%3Aclosed
Kenn
On Tue,
+1 for going by the commits since this is what matters at the end of the
day. Also, many issues may not get tagged correctly for a given release due
to either the contributor not tagging the issue or due to commits for the
issue spanning multiple Beam releases.
For example,
For all commits in a
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/29099 [Bug]: FnAPI Java
