Difference between revisions of "Serve.cfg:tester"
From EjudgeWiki
| Line 9: | Line 9: | ||
* <tt>[[serve.cfg:tester:clear_env|clear_env]]</tt> | * <tt>[[serve.cfg:tester:clear_env|clear_env]]</tt> | ||
* <tt>[[serve.cfg:tester:enable_memory_limit_error|enable_memory_limit_error]]</tt> | * <tt>[[serve.cfg:tester:enable_memory_limit_error|enable_memory_limit_error]]</tt> | ||
| + | * <code>[[serve.cfg:tester:enable_ejudge_env|enable_ejudge_env]]</code> | ||
* <tt>[[serve.cfg:tester:errorcode_file|errorcode_file]]</tt> | * <tt>[[serve.cfg:tester:errorcode_file|errorcode_file]]</tt> | ||
* <tt>[[serve.cfg:tester:error_file|error_file]]</tt> | * <tt>[[serve.cfg:tester:error_file|error_file]]</tt> | ||
Latest revision as of 07:38, 17 September 2023
Навигация: Главная страница/Система ejudge/Использование/Конфигурационные файлы/serve.cfg/Конфигурационные параметры тестирования
- abstract
- any
- arch
- check_cmd
- check_dir
- checker_env
- clear_env
- enable_memory_limit_error
enable_ejudge_env- errorcode_file
- error_file
- id
- ignore_stderr
- is_dos
- key
- kill_signal
- max_data_size
- max_stack_size
- max_vm_size
- memory_limit_type
- name
- no_core_dump
- no_redirect
- nwrun_spool_dir
- prepare_cmd
- priority_adjustment
- problem_name
- problem
- run_dir
- secure_exec_type
- skip_testing
- start_cmd
- start_env
- super
- time_limit_adj_millis
- time_limit_adjustment
