Log size

[concordium-cl]

UPDATED

The size of logs to be submitted often exceeds GitHub's upload limit of 100MB.

We've created a small tool retrieve_minified_logs to sample your full set of log files and output a summary that is acceptable for submission. Please see Logs for more details.

[senevrensel]

Well , to prune a log file is not enough . You gotta find another solution .
For mission B1 what i can suggest is cancel the submitting of log files and just check the ones who run the node 30 days in a row .
This will be much more practical and easier for you and for us.

[concordium-cl]

Thanks senevrensel, we have considered this minimal approach but decided against it. We are looking into an alternative submission at the moment.

[andrste]

Hello, so when we have been running these 7 days on B2 and B6 tasks. Do we need to pull request even without a log? so you can see who are in these top 250?

[concordium-cl]

Hi andrste, the logs can now be included in an existing submission or in a newly created one. See updated description above.

[andrste]

Thanks @concordium-admin! I have a big problem. I ran B2 & B6 and retrieved logs which are 1.9Gb each, and removed VM because I was running different VPS for different challenges. Now I saw that these log files was not retrieved fully and it shows that I was running for 5 days only, even I was running for full 7 calendar days. Now it somehow I have a snapshot of my B2 challenge server and retrieved with Mario new tool and it went very good has no big weight and shows that my B2 was running from 16 till 25 which is good. But I have a question what to do with B6, I only have this 1.9Gb log and syslog from server and I don't have a snapshot to retrieve log with new tool...