Subject: Re: bug#46722: test-map-into fails

From: Lars Ingebrigtsen <[email-masked]>
Date: Sat, 15 Jan 2022 09:01:26 +0100

Philipp Stephani <[email-masked]> writes:

> Thanks. In my case I also got flaky results for test-map-merge-empty,
> test-map-into-hash-test, test-map-merge-with, and test-map-merge, as
> well as the bindat tests (they already fail at
> loading/byte-compilation time with (cl-no-applicable-method
> bindat--type unpack (dest-ip ip) (src-ip ip) (dest-port uint 16)
> (src-port uint 16))); any objection to marking them (or even all
> affected tests) as unstable, too?

Marking the other test-map* functions as unstable (on the release
branch) should be fine.

Are the bindat tests also failing because of the map problems, or is
that unrelated? 

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no