You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically there are two types of status. One is pull_request triggered workflows and another are checks added by some publishers after tests run. "Test Results" are those checks added by "Publish JUnit Test Result" step of all java precommits. But this step does not publish to the correct tests (it attaches to a random test)
This visual glitch, though does not affect the functionality, introduces confusion to developers
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
What happened?
See https://github.com/apache/beam/actions/runs/6568261975/workflow?pr=28853:
What caused this:
Basically there are two types of status. One is pull_request triggered workflows and another are checks added by some publishers after tests run. "Test Results" are those checks added by "Publish JUnit Test Result" step of all java precommits. But this step does not publish to the correct tests (it attaches to a random test)
This visual glitch, though does not affect the functionality, introduces confusion to developers
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: