Skip to content

Running in parallel suppresses output from failed examples #1613

@rkennedy

Description

@rkennedy

I have a module whose tests include some testable examples. The examples run, and the failure is detected, but I've found that if I use ginkgo run -p to run tests in parallel, then the output of failed examples never gets printed.

Running sequentially:

$ ginkgo run .
Running Suite: Examples - /Users/Rob.Kennedy/src/ginkgo-example-bug
===================================================================
Random Seed: 1761932072

Will run 1 of 1 specs
•

Ran 1 of 1 Specs in 0.000 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
--- FAIL: ExampleFoo (0.00s)
got:
foo
want:
bar
FAIL

Ginkgo ran 1 suite in 706.842041ms

Test Suite Failed
exit status 1

Running parallel:

$ ginkgo run -p .
Running Suite: Examples - /Users/Rob.Kennedy/src/ginkgo-example-bug
===================================================================
Random Seed: 1761932054

Will run 1 of 1 specs
Running in parallel across 7 processes
•

Ran 1 of 1 Specs in 0.004 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 2.404204125s

Test Suite Failed
exit status 1

We can see above that we still get "Test Suite failed," but we're not shown what failed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions