Skip to content

[Core] Logging policy should be clearly defined and needs unit test coverage #9692

@wuisawesome

Description

@wuisawesome

What is the problem?

We currently have no unit test coverage for logging. Behavior we should cover:

  • stderr in remote tasks should be directed to driver's stderr
  • stdout in raylet and core worker should not be sent to the driver
  • stderr in raylet should be sent to stderr of driver (core worker should not)
  • explicit logging should be sent to driver's stderr

Reproduction (REQUIRED)

Please provide a script that can be run to reproduce the issue. The script should have no external library dependencies (i.e., use fake or mock data / environments):

If we cannot run your script, we cannot fix your issue.

  • I have verified my script runs in a clean environment and reproduces the issue.
  • I have verified the issue also occurs with the latest wheels.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issue, but not time-criticalbugSomething that is supposed to be working; but isn'tdocsAn issue or change related to documentationobservabilityIssues related to the Ray Dashboard, Logging, Metrics, Tracing, and/or Profilingpending-cleanupThis issue is pending cleanup. It will be removed in 2 weeks after being assigned.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions