Jared Tobin d2964581da tests: replace bogus queue in test-qeu ... Per yosoyubik's commentary in urbit/urbit#1799: The test is expecting that qeu to not be correct.. when it is. The test [98 [97 ~ ~] [100 ~ [99 ~ ~]]] is a correct queue if we look at vertical ordering: (mor 98 97), (mor 98 100) & (mor 100 99) all return %.y, so vertical ordering is correct. The previous implementation of +apt:to checked only horizontal ordering between siblings, in this case that would fail: (mor 97 100) returns %.n, but that is not how you check correctness of hoon treaps. The solution is to modify that test with a proper "incorrect" +qeu, for example: ((soft (qeu)) [97 [98 ~ ~] [100 ~ [99 ~ ~]]]). Vertical ordering is not correct with any of the children.		2019-10-10 10:20:25 +04:00
..
app	updates :acme to track order attempts across orders	2019-07-10 23:13:44 -07:00
bug	Add 'pkg/arvo/' from commit 'c20e2a185f131ff3f5d3961829bd7a3fe0f227f8'	2019-06-28 12:48:05 +08:00
lib	Reenable ring signature tests now that we've monorepoed.	2019-06-28 13:33:48 -07:00
sys	tests: replace bogus queue in test-qeu	2019-10-10 10:20:25 +04:00