Skip to content

fatalError in swift_tests executed in RBE produce a trace/BPT trap and no logs right now #1500

Open
@ed-irl

Description

@ed-irl

If a test fatalErrors, it will kill the whole test runner without any logs. Bazel does correctly report a non-0 exit code at least.

In an RBE like BuildBuddy, this produces almost no useful output.

It would be good to wrap the test runner to handle a test process that exits unexpectedly in order to provide log output and other relevant debugging information from the failed test.

There's been a lot of work on the test runner code in rules_swift lately; I'd be interested in working on this but its not clear how such a change would align to the current work in this area. If anyone can give pointers on a design I'd appreciate the feedback.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions