JOJ/JOJ3
25
6
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Update FAQ: JOJ3 usage

manuel 2025-10-07 08:46:52 +08:00
parent 2032a71cc8
commit f1cf28a5cd
1 changed files with 19 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
FAQ%3A-JOJ3-usage.md

@ -1,15 +1,17 @@
# JOJ3 FAQ
## JOJ usage
## First usage questions
**Q: I pushed my code, then what?**
A: Check the `Issues` tab in your Gitea repository, you should have received a new issue with all the details related to your last commit. This will be updated on the next push for this task, don't close it. You can also check the `Actions` tab to check more detailed logs of the run, however these information is unlikely useful to students.
A: Check the `Issues` tab in your Gitea repository, you should have received a new issue with all the details related to your last commit. Click on the small "triangles" to see more details.
**Q: Gitea shows a "red cross" and I have no idea where it comes from, what should I do?**
**Note.** This issue will be updated on the next push for this task, don't close it. You can also check the `Actions` tab to check more detailed logs of the run, however these information is unlikely useful to students.
A: A "red cross" means something "serious" happened, e.g. failed to pass health check or the source code could not compile or your program crashed while only running code is accepted. There could be many reasons... To find out your problem, check the newly updated/opened issue, carefully read the provided information, and fix your problem accordingly. Usually submissions with a red cross are considered as failed and are not graded.
**Q: For test cases I can see some unexpected `+` and `-` which are not part of my code. Where are they coming from?**
A: When running test cases two things can happen: (i) you pass, ie. your output matches the expected sample or (ii) you failed, ie. there are differences between your output and the expected sample. Extra lines are marked with `+` while missing ones appear with a `-`.
**Q: I failed the health check, how bad is it?**
@ -21,13 +23,23 @@ A: While JOJ3 and health check could have bugs, we have not seen any false posit
**Note.** Most common non-ASCII characters are Chinese characters, the Chinese equivalent to `-` or `:` can be tricky to spot.
## JOJ usage
**Q: Gitea shows a "red cross" and I have no idea where it comes from, what should I do?**
A: A "red cross" means something "serious" happened, e.g. failed to pass health check or the source code could not compile or your program crashed while only running code is accepted. There could be many reasons... To find out your problem, check the newly updated/opened issue, carefully read the provided information, and fix your problem accordingly. Usually submissions with a red cross are considered as failed and are not graded.
**Q: My program exits with a "weird" error status and a number. What does it mean?**
A: A working program should return with status (or code) 0. If something unexpected is happening JOJ or the OS might be sending a *signal* to your program. To understand what went wrong, run the following command `kill -L`. It lists all the signal names in a table. Check the name of the signal corresponding to the number you see in your Gitea issue and run a quick online search.
**Q: For test cases I can see some unexpected `+` and `-` which are not part of my code. Where are they coming from?**
**Q: I made mistake when releasing, how to release again?**
A: When running test cases two things can happen: (i) you pass, ie. your output matches the expected sample or (ii) you failed, ie. there are differences between your output and the expected sample. Extra lines are marked with `+` while missing ones appear with a `-`.
A: In some courses you might be able to release only once, or once every $x$ hours. Open the JOJ issue related to your release and check the "release rate" in Case 1 of Health check section.
If more than one release is allowed then go to release, click on the small pen on the top right of the release you want to edit and select "Delete release". Then click on "Tags" and deleted the tag corresponding to your release. Finally follow the regular release process to create a new release.
## Communication