here's the log:
....
....
....
Starting random testcases
Test Passed: Value == '[]'
STDERR
Execution Timed Out (12000 ms)
.....
.....
what should I do?
Apologies, I only looked at this kata again today. I didn't receive a notification of your comment as it wasn't labeled as Issue.
I'm not sure I follow though, can you expand? I'm trying to understand where the expectation of an i32 comes from.
The solution setup currently takes a u8 for the length parameter and returns u64, so I expected the tests to infer that type and I didn't get any of the above warnings for my own solution either. I'm not sure why yours is returning i32.
I do not undersand why the assertion checking that the last character is "/" blames me as a cheater.
I expect to be able to use the "x" parameter; which is not the case.
If I am reading the test suite correctly, there's 100 random test cases, each of them with length of the pattern generated as l <- floor(runif(1, 0, 11)). As much as I am unable to read R, I still believe you can expect a couple of test cases of length 9 or 10.
Without spoiling anything - how fast does my code have too be to pass the attempt? I've got an R-script that takes ~5s to run "E" 9 at the moment and its just not cutting the mustard.
wow! so simple, yet so complicated. thanks for the kata!
JS
the test passes
but ATTEMPT gives "exit code 1"
here's the log:
....
....
....
Starting random testcases
Test Passed: Value == '[]'
STDERR
Execution Timed Out (12000 ms)
.....
.....
what should I do?
Python translation kumited :) please review and approve ~~
You can't avoid recursion withouth avoiding recursion.
Beautiful kata. Short, with a clear idea, and withouth wasting our time with edge-cases and input caludation.
Apologies, I only looked at this kata again today. I didn't receive a notification of your comment as it wasn't labeled as
Issue
.I'm not sure I follow though, can you expand? I'm trying to understand where the expectation of an
i32
comes from.The solution setup currently takes a
u8
for thelength
parameter and returnsu64
, so I expected the tests to infer that type and I didn't get any of the above warnings for my own solution either. I'm not sure why yours is returningi32
.I do not undersand why the assertion checking that the last character is "/" blames me as a cheater.
I expect to be able to use the "x" parameter; which is not the case.
Thank you very much hobovsky
Disregard my comment
https://github.com/codewars/codewars.com/wiki/Troubleshooting-your-solution#how-can-i-see-which-input-causes-my-solution-to-fail
Hi,
My code passes the Sample Test, but if fails for the random and final tests.
In order to check it and fix it, is there any way of knowing which values are executed?
In case anyone is familiar, it expects this values:
If I am reading the test suite correctly, there's 100 random test cases, each of them with length of the pattern generated as
l <- floor(runif(1, 0, 11))
. As much as I am unable to read R, I still believe you can expect a couple of test cases of length 9 or 10.Without spoiling anything - how fast does my code have too be to pass the attempt? I've got an R-script that takes ~5s to run "E" 9 at the moment and its just not cutting the mustard.
How I can convert Dot to Int???
Loading more items...