Skip to content

Conversation

tossy310
Copy link
Member

@tossy310 tossy310 commented Sep 22, 2024

Testset がテストを実行する際に、既存の入出力ファイル名の指定に加えて、エラー出力先を指定して Solution を実行することで、今まで /dev/null に消えていた(もしくは標準出力を汚していた)テストの実行時の標準エラー出力をファイルに記録するようにします。

なお、通常のdiffやcustom judgeを使う提出に加えて、DOMJudgeReactiveRunner も対応させましたが KUPCReactiveRunner は想定挙動が分からないため、挙動が変わらないようにしています。

Fixes #101.

(CC: @climpet )

Before this change, DOMJudgeReactiveRunner ignores output file because
reactive problems don't usually have output, and interactor don't
use it.

However, when packing zip to upload, diff file is mandatory, so
even though it just creates an empty file, DOMJudgeReactiveRunner
should make sure diff file is created so that later pack and upload
won't fail due to missing diff file.

Fixes icpc-jag#102.
@tossy310
Copy link
Member Author

#103 に依存しているので後でrebaseします

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

解答コードの標準エラー出力を rime-out に保存したい
1 participant