Skip to content

End-to-end tests are unstable on CI #1855

@jleibs

Description

@jleibs

The intel-mac e2e tests were failing and in an attempt to unblock our wheel builds, I disabled them in #1853

In the commit before disabling the mac builds, the linux e2e were passing. You can see an example successful run here:

However after landing the change to disable the tests, the linux tests are now failing as well:

Running the same commit locally runs fine.

The stack trace here hints at a shutdown race condition, I think related to the multi-processing test.

[2023-04-14T17:59:28Z INFO  rerun::run] Received first message.
31
thread 'msg_encoder' panicked at 'Main thread should still be alive: "SendError(..)"', crates/re_sdk_comms/src/buffered_client.rs:203:47
32
stack backtrace:
33
[2023-04-14T17:59:34Z INFO  rerun::run] Successfully ingested 20002 messages.
34
   0: rust_begin_unwind
35
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:575:5
36
   1: core::panicking::panic_fmt
37
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/panicking.rs:64:14
38
   2: core::result::unwrap_failed
39
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/result.rs:1791:5
40
   3: re_sdk_comms::buffered_client::msg_encode

Metadata

Metadata

Assignees

No one assigned

    Labels

    😤 annoyingSomething in the UI / SDK is annoying to use🧑‍💻 dev experiencedeveloper experience (excluding CI)🪳 bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions