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
As the usage of Pascal has become a little bit low in recent years, it is no longer customary to have a Pascal compiler, if it ever had been. We have NO_JAVA_TESTS. We could also add NO_PASCAL_TESTS.
The text was updated successfully, but these errors were encountered:
IIRC, sandboxed compilation tests should work regardless of the host environment, so these should be fine as is. For system compilers, I think a better way of achieving this would be to detect presence of system fpc and skip tests depending on that, since I see no point in a manual way to disable tests except for when a necessary compiler isn't present on the system.
In general, we should check for:
presence of fpc in the host system,
presence of Java (javac/java) in the host system,
whether sio2jail can be run in the host system (ie. whether the performance counters are exposed to the system),
and disable the respective tests accordingly, and then remove the manual test disable environment variables.
As the usage of Pascal has become a little bit low in recent years, it is no longer customary to have a Pascal compiler, if it ever had been. We have
NO_JAVA_TESTS
. We could also addNO_PASCAL_TESTS
.The text was updated successfully, but these errors were encountered: