2010/8/5 Parrot <[email protected]>: > #1712: Packfile tests incorrectly try to read non-native packfiles. > ----------------------+----------------------------------------------------- > Reporter: doughera | Owner: > Type: bug | Status: new > Priority: normal | Milestone: > Component: none | Version: trunk > Severity: medium | Keywords: > Lang: | Patch: > Platform: | > ----------------------+----------------------------------------------------- > > Comment(by doughera): > > I have changed the title of this ticket to more accurately reflect one of > the main problems: The packfile tests are simply wrong. The binary > packfiles used in the tests are generated on one particular system, but > the test assumes they can be read on all systems. That is simply not > true, as this ticket demonstrates. Some of the conversions are supported, > but others are not. Until portable packfiles are implemented, this test > should be skipped. Alternatively, the packfiles required for the test > could be natively generated on the system as part of the build process.
This is simply not true. The tests are right, the native pbcs were wrong. The release manager simply forgot to update these pbc's as kid has shown. Generating and testing pseudo-pbc's will please the tests but will not check for real failure cases. The test should be improved to check for forgotton updates maybe, for newbies. Or just provide packfile version portability as it was designed this way but deleted by Allison to get out v1.0. Your are once again trying to harm to keep pbc platform portable by disabling these tests (the hilarious TT #357), on the ground that 1) pbc are not platform portable (which is not true until shown otherwise), and will never get detected if someone will break it and the native pbc tests will be disabled again, or 2) that my tests are bad, which is also not true. Unsupported conversions should be maintained in my TT #357 testmatrix, until someone comes along and apply my old patches to support the yet unsupported conversions. -- Reini Urban http://code.google.com/p/cygwin-rurban/source/browse/trunk/release/parrot#parrot/patches _______________________________________________ parrot-tickets mailing list [email protected] http://lists.parrot.org/mailman/listinfo/parrot-tickets
