diff options
| author | sterni <sternenseemann@systemli.org> | 2022-08-30T13·23+0200 |
|---|---|---|
| committer | clbot <clbot@tvl.fyi> | 2022-08-30T17·51+0000 |
| commit | 049ec229437a8c83196c96c83779ece6de971b0c (patch) | |
| tree | bc154922c64909a7d68adb0106c2e3c057b3f69c /nix/buildLisp | |
| parent | e07556493f51caa8b4644c4de375c12012b8ad18 (diff) | |
feat(nix/buildLisp): re-enable CCL r/4546
The problem went away once again, let's see how long it'll last this time. As it turns out, CCL has a Unicode Standard conforming string implementation that doesn't allow the use of (lone) surrogate code points, requiring us to disable a test in cl-json which tested the behavior of en- and decoding of such a (technically illegal) string. Change-Id: I8bfa482934bbf94f86cecdde02d5c3d4e77950a5 Reviewed-on: https://cl.tvl.fyi/c/depot/+/6204 Tested-by: BuildkiteCI Autosubmit: sterni <sternenseemann@systemli.org> Reviewed-by: tazjin <tazjin@tvl.su>
Diffstat (limited to 'nix/buildLisp')
| -rw-r--r-- | nix/buildLisp/default.nix | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/nix/buildLisp/default.nix b/nix/buildLisp/default.nix index 9d6ce4edda..4266fa18d0 100644 --- a/nix/buildLisp/default.nix +++ b/nix/buildLisp/default.nix @@ -154,8 +154,7 @@ let let implementation = old.implementation or defaultImplementation; brokenOn = old.brokenOn or [ ]; - # TODO(sterni): https://github.com/Clozure/ccl/issues/405 - targets = lib.subtractLists (brokenOn ++ [ "ccl" implementation.name ]) + targets = lib.subtractLists (brokenOn ++ [ implementation.name ]) (builtins.attrNames impls); in { |