Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnostic and comment lines are not displayed if --jobs is greater than 1 #39

Closed
W1M0R opened this issue Apr 20, 2023 · 1 comment
Closed

Comments

@W1M0R
Copy link

W1M0R commented Apr 20, 2023

Example 1

An example that works as expected (without specifying the --jobs parameter):

pg_prove -U postgres --dbname test --recurse --ext .sql --trap ./tests/
./tests/01.sql ....... 1/2
# Failed test 2: "There should be 17 disabled resources"
#         have: 17
#         want: 18
# Looks like you failed 1 test of 2
./tests/01.sql ....... Failed 1/2 subtests

./tests/02.sql .. ok
./tests/03.sql .... ok
./tests/04.sql ............. ok
./tests/05.sql ............. ok

Test Summary Report
-------------------
./tests/01.sql     (Wstat: 0 Tests: 2 Failed: 1)
  Failed test:  2
Files=5, Tests=9,  0 wallclock secs ( 0.03 usr  0.00 sys +  0.02 cusr  0.00 csys =  0.05 CPU)
Result: FAIL

Example 2

The same command but with --jobs 2, no longer produces the comment/diagnostic line:

pg_prove -U postgres --dbname test --recurse --ext .sql --trap --jobs 2 ./tests/
./tests/01.sql ....... Failed 1/2 subtests

./tests/02.sql .. ok
./tests/03.sql .... ok
./tests/04.sql ............. ok
./tests/05.sql ............. ok

Test Summary Report
-------------------
./tests/01.sql     (Wstat: 0 Tests: 2 Failed: 1)
  Failed test:  2
Files=5, Tests=9,  0 wallclock secs ( 0.03 usr  0.00 sys +  0.01 cusr  0.02 csys =  0.06 CPU)
Result: FAIL

I expected the following comment lines to appear in the output:

# Failed test 2: "There should be 17 disabled resources"
#         have: 17
#         want: 18
# Looks like you failed 1 test of 2
@theory
Copy link
Owner

theory commented Apr 20, 2023

Looks like this is an issue with Test::Harness. See Perl-Toolchain-Gang/Test-Harness#101.

@theory theory closed this as completed Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants