I bet you edited the sample tests. Copy your code, then reset the trainer.

Ok. I'll check it again

why do I see the height and width arguments being 5 and 5 at the end of your input...? with clues asking for 6...?

=> I don't know what you messed up in your logs but you messed it up. And I'm pretty sure the problem is on your side... check then resolve the issue.

Tests are incorrect. For examle in this test size of grid shold be 6x11. I can obtain the size from keys, but still my solution isn't accepted. Though my solution is correct

solve([
[ [ 3 ], [ 4 ], [ 2, 2, 2 ], [ 2, 4, 2 ], [ 6 ], [ 3 ] ],

[

[ 4 ], [ 6 ],

[ 2, 2 ], [ 2, 2 ],

[ 2 ], [ 2 ],

[ 2 ], [ 2 ],

[], [ 2 ],

[ 2 ]

]

],5 ,5)


My solution:

01110000000
11110000000
11000011011
11001111011
11111100000
01110000000


Moved all asserts to assert.equal.

And thank you for improving the asserts.

Seems fixed.

Thank you very much for your fix.

Also fixed announcing 1 000 random tests and then running 5 000. I was triggered by there being more than 1 000 random tests with goal under 5 ..

Fixed.

Math.round(Math.random()*2) gives values from 0 to 2 inclusive. Either use Math.floor or lose the *2. ( I opted for round. )

( JS, possibly others )

Please don't use assert. Use assert.equal and automatically give a useful error message on failure, with actual and expected value ( we can always print inputs ourselves ).

Everybody who used Test.expect has been screamed at for six years, and now we have to scream at people for using bare assert? Please.

JS: the random generator has some troubles:

small,big,goal = [ NaN, NaN, NaN ]
test:2 small:NaN big:NaN goal:NaN

I have fixed the solution. Plesae check now.