Skip to content

make fulltest: no -D040 and no --gc-debug with -runcore=fast,-O1,-O2 #1086

Closed
rurban opened this Issue Jul 21, 2014 · 1 comment

1 participant

@rurban
Parrot Virtual Machine member
rurban commented Jul 21, 2014

Do not switch to the gc-debug runcore when we want to test the fast runcore.
Ditto do not enable -D040 "fill I, N registers with garbage" with -O1 or -O2 optimizations.

benchmarks should also omit -D040 and --gc-debug.

Current errors with these changes in branch smoke-me/testfast-gh1086, because these are bad tests previously skipped based on a changed $ENV{TEST_PROG_ARGS} regexp.

testO1__t/op/calling.t                           (Wstat: 256 Tests: 104 Failed: 1)
  Failed test:  63
  Non-zero exit status: 1
testO2__t/compilers/imcc/syn/regressions.t       (Wstat: 256 Tests: 21 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
testO2__t/op/calling.t                           (Wstat: 256 Tests: 104 Failed: 1)
  Failed test:  63
  Non-zero exit status: 1
@rurban rurban added the Step-test label Jul 21, 2014
@rurban rurban self-assigned this Jul 21, 2014
@rurban rurban added a commit that referenced this issue Jul 21, 2014
@rurban rurban [test] no gc-debug runcore when testing the fast runcore
With make fulltest and variants (t/fullharness) we omit -D040 and --gc-debug
when testing -f -O1 -O2 and the various set_usual_target() tests.
This caught some -O1/-O2 errors and speeds up the fulltest suite.
We only need to run a full GC after each op and randomize the N/I regs with the
normal internal testsuite, but not the extensions and various other tests.

See [GH #1086]

Current errors:
  testO1__t/op/calling.t, testO2__t/op/calling.t,
  testO2__t/compilers/imcc/syn/regressions.t
9daa2a4
@rurban rurban added a commit that referenced this issue Jul 21, 2014
@rurban rurban [test] adjust bad -O1/-O2 test regex
with the new fullharness settings there is no space before -O1 anymore.
Fixes GH #1086
143d57b
@rurban rurban added a commit that referenced this issue Sep 6, 2014
@rurban rurban [test] no gc-debug runcore when testing the fast runcore
With make fulltest and variants (t/fullharness) we omit -D040 and --gc-debug
when testing -f -O1 -O2 and the various set_usual_target() tests.
This caught some -O1/-O2 errors and speeds up the fulltest suite.
We only need to run a full GC after each op and randomize the N/I regs with the
normal internal testsuite, but not the extensions and various other tests.

See [GH #1086]

Current errors:
  testO1__t/op/calling.t, testO2__t/op/calling.t,
  testO2__t/compilers/imcc/syn/regressions.t
fbf1f73
@rurban rurban added a commit that referenced this issue Sep 6, 2014
@rurban rurban [test] adjust bad -O1/-O2 test regex
with the new fullharness settings there is no space before -O1 anymore.
Fixes GH #1086
613a703
@rurban rurban added a commit that referenced this issue Sep 6, 2014
@rurban rurban [test] no gc-debug runcore when testing the fast runcore
With make fulltest and variants (t/fullharness) we omit -D040 and --gc-debug
when testing -f -O1 -O2 and the various set_usual_target() tests.
This caught some -O1/-O2 errors and speeds up the fulltest suite.
We only need to run a full GC after each op and randomize the N/I regs with the
normal internal testsuite, but not the extensions and various other tests.

See [GH #1086]

Current errors:
  testO1__t/op/calling.t, testO2__t/op/calling.t,
  testO2__t/compilers/imcc/syn/regressions.t
58efe74
@rurban rurban added a commit that referenced this issue Sep 6, 2014
@rurban rurban [test] adjust bad -O1/-O2 test regex
with the new fullharness settings there is no space before -O1 anymore.
Fixes GH #1086
c26a778
@rurban rurban added this to the 6.9.0 milestone Oct 4, 2014
@rurban rurban added a commit that referenced this issue Oct 4, 2014
@rurban rurban [test] no gc-debug runcore when testing the fast runcore
With make fulltest and variants (t/fullharness) we omit -D040 and --gc-debug
when testing -f -O1 -O2 and the various set_usual_target() tests.
This caught some -O1/-O2 errors and speeds up the fulltest suite.
We only need to run a full GC after each op and randomize the N/I regs with the
normal internal testsuite, but not the extensions and various other tests.

See [GH #1086]

Current errors:
  testO1__t/op/calling.t, testO2__t/op/calling.t,
  testO2__t/compilers/imcc/syn/regressions.t
a0f0195
@rurban rurban added a commit that referenced this issue Oct 4, 2014
@rurban rurban [test] adjust bad -O1/-O2 test regex
with the new fullharness settings there is no space before -O1 anymore.
Fixes GH #1086
1c1d7ca
@rurban rurban added a commit that referenced this issue Oct 4, 2014
@rurban rurban [cage] ChangeLog for GH #1086 da4cc65
@rurban
Parrot Virtual Machine member
rurban commented Oct 4, 2014

Merged into 6.9.0 master

@rurban rurban closed this Oct 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.