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

harness6 runs incorrect number of tests when spec or stresstesting #6166

Closed
p6rt opened this issue Mar 29, 2017 · 3 comments
Closed

harness6 runs incorrect number of tests when spec or stresstesting #6166

p6rt opened this issue Mar 29, 2017 · 3 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Mar 29, 2017

Migrated from rt.perl.org#131075 (status was 'resolved')

Searchable as RT131075$

@p6rt
Copy link
Author

p6rt commented Mar 29, 2017

From @dogbert17

When running spectest (or stresstest) under harness6 not all files in spectest.data that should be run are being run. For example​:

'make spectest TEST_JOBS=3', i.e. harness5 tests 1168 files

on the other hand

'make spectest HARNESS_TYPE=6 TEST_JOBS=3' only tests 1160 files

The two harnesses should test the same number of files. There's reason to believe that the bug hides in harness6.

@p6rt
Copy link
Author

p6rt commented Mar 29, 2017

From @dogbert17

On Wed, 29 Mar 2017 09​:52​:00 -0700, jan-olof.hendig@​bredband.net wrote​:

When running spectest (or stresstest) under harness6 not all files in
spectest.data that should be run are being run. For example​:

'make spectest TEST_JOBS=3', i.e. harness5 tests 1168 files

on the other hand

'make spectest HARNESS_TYPE=6 TEST_JOBS=3' only tests 1160 files

The two harnesses should test the same number of files. There's reason
to believe that the bug hides in harness6.

Fixed with commit 876637010edef3155953cda3ea2cff57f7d7dd07

@p6rt p6rt closed this as completed Mar 29, 2017
@p6rt
Copy link
Author

p6rt commented Mar 29, 2017

@dogbert17 - Status changed from 'new' to 'resolved'

@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant