Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created February 16, 2018 22:20
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Whateverable/48deadf085d67157c66284bd34fc2e85 to your computer and use it in GitHub Desktop.
Save Whateverable/48deadf085d67157c66284bd34fc2e85 to your computer and use it in GitHub Desktop.
bisectable6
old=2018.01 chdir ‘sandbox/roast’; run env=>%(%*ENV, PERL6LIB=>‘packages’, MVM_SPESH_NODELAY=>1), ‘perl6’, ‘S32-str/windows-1251-windows-1252-encode-decode.t’
Bisecting: 101 revisions left to test after this (roughly 7 steps)
[752bb8b381a06dd4d49247d36369fffa3327a641] Re-design Whatever currier
»»»»» Testing 752bb8b381a06dd4d49247d36369fffa3327a641
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing 23a8aa87b03f6ad18089fba3681ef4d176d125be
»»»»» Script output:
1..4
ok 1 - Test encoding from Unicode to windows-1252
ok 2 - Test decoding from windows-1252 to Unicode
ok 3 - Test encoding from Unicode to windows-1251
ok 4 - Test decoding from windows-1251 to Unicode
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 2c36ab2ef94b3f94053be4880ab19cbfca5af617
»»»»» Script output:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» Script exit code: 1
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 01ce5632bc9a4359870fa9c68347b9217d949995
»»»»» Script output:
1..4
ok 1 - Test encoding from Unicode to windows-1252
ok 2 - Test decoding from windows-1252 to Unicode
ok 3 - Test encoding from Unicode to windows-1251
ok 4 - Test decoding from windows-1251 to Unicode
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 902f45f508badcc147d685e17ecd52d1f86154a8
»»»»» Script output:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» Script exit code: 1
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing ddda7439747ae667b513a5a7dc2b7f16af1a269f
»»»»» Script output:
1..4
ok 1 - Test encoding from Unicode to windows-1252
ok 2 - Test decoding from windows-1252 to Unicode
ok 3 - Test encoding from Unicode to windows-1251
ok 4 - Test decoding from windows-1251 to Unicode
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 646266ae70a6b759637e5a9da6fcf8778840fb1d
»»»»» Script output:
1..4
ok 1 - Test encoding from Unicode to windows-1252
ok 2 - Test decoding from windows-1252 to Unicode
ok 3 - Test encoding from Unicode to windows-1251
ok 4 - Test decoding from windows-1251 to Unicode
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 4507a5654108fdaff0254f439a7f593ce90a1849
»»»»» Script output:
1..4
ok 1 - Test encoding from Unicode to windows-1252
ok 2 - Test decoding from windows-1252 to Unicode
ok 3 - Test encoding from Unicode to windows-1251
ok 4 - Test decoding from windows-1251 to Unicode
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing c73cb78fbaa9c83be2ad6c5919291dfe9d635609
»»»»» Script output:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» Script exit code: 1
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1..4
Error encoding Windows-1252 string: could not encode codepoint 8250
in sub test_encode at S32-str/windows-1251-windows-1252-encode-decode.t line 13
in sub run_test at S32-str/windows-1251-windows-1252-encode-decode.t line 17
in block <unit> at S32-str/windows-1251-windows-1252-encode-decode.t line 9
# Looks like you planned 4 tests, but ran 0
The spawned command 'perl6' exited unsuccessfully (exit code: 255)
in block <unit> at /tmp/IM5l8MtyBX line 1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
4507a5654108fdaff0254f439a7f593ce90a1849 is the first new commit
commit 4507a5654108fdaff0254f439a7f593ce90a1849
Author: Samantha McVey <samantham@posteo.net>
Date: Thu Feb 1 17:47:12 2018 -0800
Bump Moar/NQP to get support for windows-1251 (Cyrllic) encoding
MoarVM Changes: 2018.01-53-g7fdc6aa..2018.01-55-g823cd43dd
823cd43dd Add windows-1251 (Cyrillic) decode/encode. Fix bug in windows-1252
6306b824a Add script to generate Windows-1251 and 1252 codetables
:040000 040000 66f24ed1aefd83f1a5be70729ec0426beaf79052 7bb27e4de91c9cd2108809ed8705193dafde4870 M tools
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment