False "--run-time limit reached" log on stopping

[deepjia]

Prerequisites

• I am using the latest version of Locust
• I am reporting a bug, not asking a question

Description

When stop()/quit() is called, the terminal prints --run-time limit reached, shutting down, although this is not actually due to reaching the specified --run-time parameter."​​

Command line

locust -f main.py --web-port 8080 --csv report --processes 8 --autostart --autoquit 5 --run-time 5m

Locustfile contents

stop or quit manually

Python version

3.12

Locust version

2.37.14

Operating system

linux (based on centos

[deepjia]

def stop_and_optionally_quit():
        if options.autostart and not options.headless:
            logger.info("--run-time limit reached, stopping test")

seems not a proper condition in locust/main.py

[cyberw]

Yea that is statement is a guess rather than hard evidence for the run time limit being reached. Not sure if there is an easy fix for it though.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 20 days.

[deepjia]

Yea that is statement is a guess rather than hard evidence for the run time limit being reached. Not sure if there is an easy fix for it though.

I think it's not very appropriate to directly describe it as "--run-time limit reached" when it's unclear why it stopped. When the reason for stopping is uncertain, it's inappropriate to simply label it as "--run-time limit reached". I suggest either omitting this description, or - if there's a compelling reason to include it - making it explicitly clear that this is only a guess.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 20 days.