Skip to content

Global logger and tracing subscribers are set multiple times in tests #712

Description

@Bowen951209

Hello. I'm new to valence!

HEAD: 2b70535

I just ran cargo test and saw a lot of same errors coming up:

ERROR bevy_log: Could not set global logger and tracing subscriber as they are already set. Consider disabling LogPlugin.

This is because LogPlugin is initialized multiple times when running multiple tests together.
No error would pop up if only running a single test at a time.

How should we address this? Should we just disable LogPlugin in valence::testing::ScenarioSingleClient::new?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions