Welcome and good luck!
Welcome to the Marathon Match Tournament Final 2025! This problem was written by me and tested by @JacoCronje and @nika.
If you have any technical questions or issues then please ask them in this forum.
Good luck and have fun!
Welcome to the Marathon Match Tournament Final 2025! This problem was written by me and tested by @JacoCronje and @nika.
If you have any technical questions or issues then please ask them in this forum.
Good luck and have fun!
Comments
As I wrote in the "Welcome" forum, my submission from >1h ago is still in queue, and I also can't see the ranking, is something broken?
We are looking into it.
Can you please submit again.
My last submission, half an hour after your message, was still broken
I assume numerical results are now correctly shown; can you also fix the ranking order? Seems to still take into account the 100s from before.
We're working on that part too now.
At least we are now getting some results and artifacts.
My latest submission has have proper example output artifact.
But there was a problem when running (provisional?)
I did resubmit, but same happened
2025-11-22 14:05:28 info: DATA Testing cycle completed
2025-11-22 14:05:28 error:
2025-11-22 14:05:28 error: { Error: ENOENT: no such file or directory, open '/home/ubuntu/tc-mm-processor/submissions/dn3kBupch6TIOg/submission/artifacts/private/current.json'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object.handle (/home/ubuntu/tc-mm-processor/src/services/KafkaHandlerService.js:229:36)
at process._tickCallback (internal/process/next_tick.js:68:7)
errno: -2,
syscall: 'open',
code: 'ENOENT',
path:
'/home/ubuntu/tc-mm-processor/submissions/dn3kBupch6TIOg/submission/artifacts/private/current.json' }
2025-11-22 14:05:28 error: Error: ENOENT: no such file or directory, open '/home/ubuntu/tc-mm-processor/submissions/dn3kBupch6TIOg/submission/artifacts/private/current.json'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object.handle (/home/ubuntu/tc-mm-processor/src/services/KafkaHandlerService.js:229:36)
at process._tickCallback (internal/process/next_tick.js:68:
I'm getting the same error.
Also, on my first submit I got the full list of test seeds it seems. It is not there on the second run.
Are these seeds changed or was the list given to all?
I also got suspicious artifact from first successful submit (ignored it), not example output.
(edit: successful submit, my very first submit has gone to void it seems)
magically those my afternoon submissions got score an hour ago
but my latest has the same problem again
I just made my first submission and it failed with the same errors about current.json, even though the scores in output.txt look fine. Is there any official word on this?
After some time, the failure was replaced by a proper score.
t looks think the "example" run (seeds 1-10) is running under the name "provisional" instead, which results in a failure being reported, but eventually the proper "provisional" run happens and a score appears. If you want to see the output for seeds 1-10, you have to download the "provisional" artifacts before they are replaced by the actual "provisional" run.
if it is still that is how it is...
someone from topcoder please decide (confirm?) if it is allowed to check provisional seeds/score?
because that normally that should not be available!
but as now example run is not consistently available we might need to check what we have
I don't see provisional seeds/scores. I see the usual example 1-10 seeds/scores, but I get them by downloading the artifact called "provisional". Eventually it is replaced by the real "provisional" artifact that has an empty output.txt.
Oh wait -- there is also a scores.json that has information about the 100 provisional seeds. Hmm. Shouldn't affect final judging anyway.
@dimkadimon?
We are about the change the seeds for the provisional tests and deploy a fix that should prevent them from being leaked again.
Try not to use the leaked seeds, it will be better to ignore them.
another submit totally to void (submit#7)
interestingly the page sometimes shows 6 submits for me, sometimes 8