Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record testcase directory in judging runs. #2324

Merged
merged 1 commit into from
Feb 23, 2024
Merged

Conversation

meisterT
Copy link
Member

This makes it much easier to find out where to go for debugging.

Fixes #2059.

Example:
image

Clicking the copy/paste icon copies the full path.

@meisterT
Copy link
Member Author

This is an alternative to #2211

@meisterT meisterT requested review from eldering and vmcj February 12, 2024 19:58
Copy link
Member

@vmcj vmcj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me, lets see which one @eldering wants.

This makes it much easier to find out where to go for debugging.
@eldering
Copy link
Member

Fine by me, lets see which one @eldering wants.

I think this solution is better than #2211 : both in the place/way the information is displayed and also by taking the actual directory from the judgehost instead of depending on configure/build time variables.

@meisterT meisterT added this pull request to the merge queue Feb 23, 2024
Merged via the queue into DOMjudge:main with commit 28916f6 Feb 23, 2024
20 checks passed
@meisterT meisterT deleted the f2059 branch February 23, 2024 06:14
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.

Testcase in output/judgings/... directory is not easily matched with web UI
4 participants