You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even after applying the workaround in #20, compiler-tests-suite still cannot check for negative answers (or in fact any answer not in the range 0-255). For example,
Let's say we have a var_test_5.rkt file with simple content
(- 1)
and when you run racket run-tests.rkt, it will generate error like
Expected Behavior (assuming your compiler implementation is correct)
All tests should pass
Cause
compiler-tests-suite uses exit code to check result. However, on most system, exit code will be truncated to the lowest 8-bit (0-255), such that -1 became 255.
Workaround
Modify your self-defined var_test to return a nonnegative number.
The text was updated successfully, but these errors were encountered:
Description
Even after applying the workaround in #20,
compiler-tests-suite
still cannot check for negative answers (or in fact any answer not in the range 0-255). For example,Let's say we have a
var_test_5.rkt
file with simple contentand when you run
racket run-tests.rkt
, it will generate error likeExpected Behavior (assuming your compiler implementation is correct)
All tests should pass
Cause
compiler-tests-suite
uses exit code to check result. However, on most system, exit code will be truncated to the lowest 8-bit (0-255), such that -1 became 255.Workaround
Modify your self-defined var_test to return a nonnegative number.
The text was updated successfully, but these errors were encountered: