I've just started using Tools/autotest.py, and it takes a very long time to run--about 40 minutes. Is this expected?
It looks like a lot of the time is spent waiting for the simulated arducopter to descend. E.g. I see a starting altitude of 350 m and the descent rate is approx 0.5 m/s.
Not quite the expected behavior. Normal behavior has the tests completing in under 20 minutes.
However, 2.6 has slightly different throttle scaling an descent behavior, so the autotest.py default throttle levels for hover, climb and descent are now "off". That's causing simulator failure. It will be fixed shortly I believe. I am working on it too.
Here's what a "correct" autotest looked like:
Here's the broken one:
OK, thanks for the info, Andreas.