Problem data.yaml test_policy

What happens

Hi, we have a problem in data.yaml doc that makes impossible pass test_policy (most of the time)

What do you understand or find about that problem

In the last modification on the data.yaml doc there are a little problem, min_step and max_step are equal to 1 for only_clojurescript, due to that the unique way to pass test_policy is with only one exact value for complexity which is impossible most of the time.

You make any workaround? What did you do?

If my actual complexity is 2.50 my next complexity only can be 3.50 that’s a problem 'cause is difficult find a exact value for accomplish that.


someone else find the same problem: Stuck due test policy there are a pipeline to show the error that we are getting

I need help with

If the max_step is a little more higher, we will have a range to work without problem .

1 Like

The problem was resolved and as you recommended, increasing the max_step. You can try again without problem!!

1 Like