Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Failing Test]: Prism runner execution test failing on Java11 #32911

Closed
17 tasks
Abacn opened this issue Oct 23, 2024 · 0 comments · Fixed by #32912
Closed
17 tasks

[Failing Test]: Prism runner execution test failing on Java11 #32911

Abacn opened this issue Oct 23, 2024 · 0 comments · Fixed by #32912

Comments

@Abacn
Copy link
Contributor

Abacn commented Oct 23, 2024

What happened?

Apparently on Java11 console output has fancy colors, which fails assert:

image

expected to contain:
    INFO Serving JobManagement endpoint=localhost:5555
but was:
    ?[2m?[37m[2024-10-23T18:04:52.324084899Z]?[0m ?[42m?[30m INFO ?[0m ?[32mServing JobManagement?[0m
    ?[34m*?[0m ?[35mendpoint?[0m: ?[4m?[34mlocalhost:5555?[0m?[0m
    
    ?[2m?[37m[2024-10-23T18:04:52.328261009Z]?[0m ?[42m?[30m INFO ?[0m ?[32mServing WebUI?[0m
    ?[34m*?[0m ?[35mendpoint?[0m: ?[4m?[34mhttp://localhost:8074?[0m?[0m
    
    
	at app//org.apache.beam.runners.prism.PrismExecutorTest.executeWithCustomArgumentsThenStop(PrismExecutorTest.java:89)

Issue Failure

Failure: Test is continually failing

Issue Priority

Priority: 2 (backlog / disabled test but we think the product is healthy)

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: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant