-
Notifications
You must be signed in to change notification settings - Fork 5
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
Input format question: final newline? #140
Comments
I made a minimal change that only makes my solution tolerant of missing newlines without any additional optimizations: mkfmnn/aoc2024-codspeed@a339d42 If you're willing to redo the day1 run for my repo, I'd really appreciate it 😄 |
Hey, I am sorry that your solutions did not work because they expected the newline to be present, but for fairness to the other participants, we will not do re-runs for previous days. Hopefully now that you know it, next runs will work better! To determine your time, you can set up CodSpeed on your repo and bench your solutions. |
|
Hey @mkfmnn, @ThomAub, as stated above, we reran your solutions on the same commits, and they worked 🥳 |
Just below the points ! Thanks for the extra effort ❤️ |
I saw my day1 solution panicked with an error in the parsing code when run by the GitHub action: https://github.com/CodSpeedHQ/Advent/actions/runs/12124386193/job/33802001005
I do know that my code made some assumptions about the input based on the input file that I got from the AoC website (for instance that each line consists of two 5 digit numbers separated by 3 spaces) which could have triggered the panic. However, looking at the leaderboard, the top submissions made similar assumptions.
I did successfully test my code against the
rust-runner
tool as described in the README. I think one thing that could have triggered the error in the code for me is if the input file supplied to the code when run in the GitHub action is missing the final newline on the last line. Could you confirm whether this is the case?Looking through the runs I did find another one that looks like it could have failed for the same reason. A few successful solutions that I spot-checked don't seem to care about whether the final line is properly terminated or not (either because they use
lines()
to split the input, or because they hard-code that the input has exactly 1000 lines).Thanks!
The text was updated successfully, but these errors were encountered: