You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
t27b lane 4: four specs blocked by spec defects (dqn, hex, gen_image, args) #7372
Four specs are on the t27b ledger as blocked, but the blocker is in the spec, not in the backend. Each one also passes the reference for a reason that checks nothing.
specs/ml/rl/dqn.t27: the tests call default_input() and valid_input(), which are declared nowhere, and assert then true. The fns ignore their inputs.
specs/tri/crypto/hex.t27: encode(codec) -> void and decode(input) -> void are empty. Their tests assert result == undefined on a void result.
specs/port/trinity/src/tri/gen_image.t27: Image_init, Image_setPixel and Image_deinit have the body undefined; and take *std.mem.Allocator. No test calls them, and one test asserts always_true() == true.
specs/tri/utils/args.t27: parse(allocator) -> void does _ = allocator;, and its one test is then true. ci-gates section 342 records that the Lean model of this fn was provable only because it split the dotted type into three parameters.
The fix is on the spec side, from the source each port names:
Activity
specs: dqn, hex, gen_image, args rewritten from their sources with re…
specs: dqn, hex, gen_image, args rewritten from their sources with re…