2009/3/8 Parrot <[email protected]>:
> #357: Enable meaningful testing of t/native_pbc/*.t
> ------------------------------+---------------------------------------------
> Reporter: doughera | Owner: rurban
> Type: cage | Status: reopened
> Priority: normal | Milestone: 1.0
> Component: none | Version:
> Severity: medium | Resolution:
> Keywords: 64bit needreview | Lang:
> Patch: applied | Platform:
> ------------------------------+---------------------------------------------
> Changes (by doughera):
>
> * status: closed => reopened
> * resolution: fixed =>
>
>
> Comment:
>
> I have reopened this ticket because you have not addressed the main
> problem: The tests done during normal development testing are not the
> same as those done on a release. To be specific: Step 2g of the release
> manager's guide instructs the release manager to change all the *.pbc
> files. Thus the files in the release will not be the ones that were
> tested.
Sorry, the main problem is already addressed.
It is in the guide, that the release manager should test and fix the
failing tests if required.
Please check with C<prove t/native_pbc/*.t>
This was not done in 0.9.1
Do you have better suggestions?
Not instructing to stamp the pbc's will not change anything, since the
tests only check the bytecode version, not the parrot version, so the
test logic remains the same.
What was done:
- fix pbc_header.pl --upd which broke the pbcs
- sanify the test logic to easily skip and todo failing tests for
all combinations
- better skip messages to bug the tester to update his pbcs if we have a
combination which requires an update.
- improved the mk_native_pbc script to get more updates
- regularly update the pbcs
What was not done:
- fix the known 64 bit bug. patch in TT #254
- add more converters (TT#387, TT #254)
--
Reini Urban
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
