mirror of
https://github.com/MaSzyna-EU07/maszyna.git
synced 2026-11-15 18:44:12 +01:00
03a417c7b0
A test run that hung, in the loading or anywhere else, waited until whoever started it killed it. A watchdog thread now ends a run still going test.wall_timeout seconds of real time after the start of the simulator, loading included: it says `test: timeout ... still running after N s of real time` and quits with the timeout code, whatever the main thread is doing, with no dialog. A test that has ended but whose simulator doesn't close ends with its own result. The limit is test.wall_timeout (settings, the scenery's config block) or --test-wall-timeout, which wins. Not given, it is test.timeout + 600 s: ten minutes for the loading, and a simulation that runs at least as fast as real time is never cut short. test.timeout 0 means no watchdog unless the limit is given; test.wall_timeout 0 turns it off. run.py passes the case's timeout as --test-wall-timeout and kills a simulator only 30 s after it. A timeout from the watchdog counts as wall_timeout there, so a run that hung doesn't pass a case expecting the simulation time to run out; test_mode_wall_timeout ends while loading on a limit of 2 s.
75 lines
2.9 KiB
C++
75 lines
2.9 KiB
C++
/*
|
|
This Source Code Form is subject to the
|
|
terms of the Mozilla Public License, v.
|
|
2.0. If a copy of the MPL was not
|
|
distributed with this file, You can
|
|
obtain one at
|
|
http://mozilla.org/MPL/2.0/.
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include "simulation/simulationtestrules.h"
|
|
|
|
#include <atomic>
|
|
#include <mutex>
|
|
#include <string_view>
|
|
#include <thread>
|
|
|
|
// integration test mode (eu07 --test -s <scenery>, eu07/maszyna#541): the scenery runs unattended in a tight
|
|
// fixed-step loop and the simulator quits with an exit code saying how the test went
|
|
namespace simulation {
|
|
|
|
class test_manager {
|
|
|
|
public:
|
|
// name of the memory cell a scenery reports its result to
|
|
static constexpr std::string_view result_cell { "__test.result" };
|
|
// fixed simulation time step of one frame in test mode [s]: 3 physics steps of 10 ms
|
|
static constexpr double frame_step { 0.03 };
|
|
|
|
// creates the result cell; called with the other scripting interface cells, before the scenery is read
|
|
void init_result_cell() const;
|
|
// the simulation is ready: start the clocks
|
|
void start();
|
|
// checks the end conditions after a simulation frame of Deltatime seconds
|
|
void update(double Deltatime);
|
|
// reported by a driver whose train went past a signal showing stop
|
|
void signal_passed_at_danger(std::string_view Vehicle, std::string_view Signal);
|
|
// ends the test with given result and closes the application; the first call wins
|
|
void finish(test_result Result, std::string_view Reason);
|
|
// ends the test with given result, without closing the application: for the ways out that close it anyway
|
|
// (a bad command line, a failed start, an exception). returns false if the test had already ended
|
|
bool conclude(test_result Result, std::string_view Reason);
|
|
// (re)sets the real time limit of the run [s] since the start of the simulator, 0 = none. the first limit
|
|
// starts the watchdog, which ends a run still going at the limit with the timeout code, whatever it's doing
|
|
void watch_wall_clock(double Limit);
|
|
|
|
bool finished() const { return m_finished; }
|
|
// exit code of the process: the result, or error while the test hasn't finished
|
|
int exit_code() const;
|
|
|
|
private:
|
|
// the watchdog's check, at Elapsed seconds of real time since the start of the simulator
|
|
void check_wall_clock(double Elapsed);
|
|
|
|
// the watchdog may end the test from its own thread
|
|
mutable std::mutex m_lock;
|
|
bool m_started { false };
|
|
std::atomic<bool> m_finished { false };
|
|
test_result m_result { test_result::error };
|
|
test_progress m_progress;
|
|
std::atomic<double> m_walllimit { 0.0 }; // [s] since the start of the simulator, 0 = none
|
|
std::jthread m_watchdog;
|
|
};
|
|
|
|
// the test of the run
|
|
test_manager &test();
|
|
|
|
// the settings of the test mode, over whatever the settings files and the scenery say: applied once the command
|
|
// line is read, and again after each config block of the scenery, which could turn the sound, the network or the
|
|
// program run at the end back on
|
|
void apply_test_mode_settings();
|
|
|
|
} // namespace simulation
|