SuccessChanges

Summary

  1. QEMU tests: IDC needs trimming as well in order to get deterministic results
  2. QEMU tests: trim calls-main-basic.idc until matching the "needle" md5 (hopefully this trick will get repeatable results on faster PCs)
  3. QEMU tests: 5D2 IDC test not deterministic (functions are the same, but comments are not)
  4. QEMU: do not use non-printable task names (VxWorks: current_task is set before it has a valid name)
  5. QEMU: backout parts of 8e29c15 large timeout didn't solve the repeatability issue - results are still sensitive to processing speed some models keep running in a loop, and after 10-20 seconds, they "discover" a new function and so on
Changeset 13712:c3ba92dba02b by alex@thinkpad:
QEMU tests: IDC needs trimming as well in order to get deterministic results
The file was modifiedcontrib/qemu/tests/run_tests.sh (diff)
Changeset 13711:47136afb2516 by alex@thinkpad:
QEMU tests: trim calls-main-basic.idc until matching the &quot;needle&quot; md5<br>(hopefully this trick will get repeatable results on faster PCs)
The file was modifiedcontrib/qemu/tests/run_tests.sh (diff)
Changeset 13710:8677809677fb by alex@thinkpad:
QEMU tests: 5D2 IDC test not deterministic (functions are the same, but comments are not)
The file was modifiedcontrib/qemu/tests/5D2/calls-main.md5 (diff)
Changeset 13709:4f0863dc644c by alex@thinkpad:
QEMU: do not use non-printable task names<br>(VxWorks: current_task is set before it has a valid name)
The file was modifiedcontrib/qemu/eos/eos.c (diff)
The file was modifiedcontrib/qemu/tests/1000D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/400D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/40D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/450D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/run_tests.sh (diff)
Changeset 13708:ee74ce939ee5 by alex@thinkpad:
QEMU: backout parts of 8e29c15<br>large timeout didn&#039;t solve the repeatability issue - results are still sensitive to processing speed<br>some models keep running in a loop, and after 10-20 seconds, they &quot;discover&quot; a new function and so on
The file was modifiedcontrib/qemu/tests/1000D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/1100D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/1200D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/40D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/450D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/500D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/600D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/60D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/70D/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/EOSM/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/EOSM2/calls-main.md5 (diff)
The file was modifiedcontrib/qemu/tests/run_tests.sh (diff)