time-wall field in meta file sometimes contains invalid value like 0.-192

Hello, I am developing an online judge system using **isolate**. I noticed that the meta file sometimes contains an unexpected time-wall value such as `0.-192.` Here is the command I used: ```shell wsl -d ubuntu -u root -- \ isolate \ --box-id=BOX_ID \ --processes=128 \ --dir=/usr/lib/jvm \ --dir=/etc/java-17-openjdk/security \ --dir=FILE_PATH \ --dir=TESTCASE_PATH \ --stdin=TESTCASE_PATH/TESTCASE_NUM.in \ --stdout=TESTCASE_NUM_output.txt \ --stderr=TESTCASE_NUM_err.txt \ --time=TIME_LIMIT \ --mem=4096000 \ --meta=META_FILE \ --run \ -- \ /usr/lib/jvm/java-17-openjdk-amd64/bin/java \ -Xms1024m -Xmx1920m -Xss512m -Dfile.encoding=UTF-8 -XX:+UseSerialGC \ Main ``` Here is the meta file output I received: ```text time:0.167 time-wall:0.-192 //This is the problem max-rss:40160 csw-voluntary:468 csw-forced:5 exitcode:0 ``` Could you please explain why the `time-wall` value sometimes appears as `0.-192` and whether this indicates a bug in isolate or a configuration issue in my environment?