#1922: Review Parrot's 'make help'
---------------------+------------------------------------------------------
Reporter: jkeenan | Owner: jkeenan
Type: cage | Status: assigned
Priority: normal | Milestone:
Component: docs | Version: 2.10.0
Severity: low | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Changes (by jkeenan):
* cc: mikehh (added)
Comment:
`make coretest` and `make smolder_coretest` are currently dysfunctional.
They give failures here in the same contexts in which `make test` and
`make smolder_test` give PASSes.
{{{
Test Summary Report
-------------------
t/pmc/packfile.t (Wstat: 0 Tests: 45 Failed: 14)
Failed tests: 12-21, 28-30, 43
t/pmc/packfileannotations.t (Wstat: 0 Tests: 17 Failed: 1)
Failed test: 2
t/pmc/packfileconstanttable.t (Wstat: 0 Tests: 13 Failed: 3)
Failed tests: 1-3
Parse errors: Bad plan. You planned 15 tests but ran 13.
t/pmc/packfiledirectory.t (Wstat: 0 Tests: 20 Failed: 5)
Failed tests: 5-6, 18-20
Parse errors: Bad plan. You planned 17 tests but ran 20.
t/pmc/packfilerawsegment.t (Wstat: 0 Tests: 7 Failed: 3)
Failed tests: 1-2, 5
Files=222, Tests=7497, 80 wallclock secs ( 0.95 usr 0.55 sys +
46.64 cusr 12.62 csys = 60.76 CPU)
Result: FAIL
}}}
IIRC, there has been on-and-off discussion in recent months as to where we
draw the boundary between 'Parrot core' and 'Parrot non-core'. This
question then spills over into the boundary between `make coretest` and
`make test`. These ''t/pmc/packfile*.t'' tests are apparently falling on
the 'wrong' side of the boundary at the moment.
This should probably be a separate TT or post to parrot-dev, but I'm
logging the problem here as part of the `make help` review.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1922#comment:11>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
