Download size of game logs from portal

Entelect Challenge 2020
1

HI guys.
Just want to check with you: what compression (if any) is being applied to the game logs (downloaded from the portal) at this time?

Yesterday I downloaded 188Mb worth of logs (zip file)…which I could locally compress to a zip file of about 5Mb.
7z goes down to under a Mb.

2 Likes
2

Hm, this seems perhaps a bit more urgent with the WACS cable breakage

3

I’m in agreement here, especially if the game run shows as requiring attention and it runs fine on my local.

1 Like
4

Had to boot up my remote server and download the logs there with a faster connection.

5

I have noticed (with a very basic, essentially “accelerate only” bot) that there are still occasional timeout s (triggering the “needs attention” flag).

I assume , atm , that this is simply because resources are not ramped up to “prod levels” currently,so occasionally things take more than a moment to startup.

Anyway, I hope that is what I’m seeing…

6

I logged a different topic for that. Reference bot seems to be the issue here.

1 Like
7

Hi @demaniak,

I will check in to see if the team can reduced the size of log downloads.

1 Like
8

@styphoiz , I have a suspicion it is the Java GC kicking in.

9

I’ve had these ones as well with the reference bot

Downloading game engine
Downloading 2020.1.2.zip
Extracting zip: engine-47549c02-8976-4cca-86ac-68c1bf2ae267.zip
Retrieving bot path from directory
Downloading bots
Downloading entries/main/d28da8b6-8c9b-4f2c-bdcc-b13244487a1e/53e3e514-e5b0-4f3a-a035-748aa8f148b8/binaries/53e3e514-e5b0-4f3a-a035-748aa8f148b8.zip
Downloading reference-bots/2020-1-2/reference-bot.zip
Extracting zip: player-523c19d3-1826-4850-81f0-26a642b5604b.zip
Extracting zip: player-dfcdfc0c-a390-450b-83af-57d15d7ce91a.zip
Config for player A : tournament-tmp/extracted/player-523c19d3-1826-4850-81f0-26a642b5604b/53e3e514-e5b0-4f3a-a035-748aa8f148b8
Failed call: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Retrying request: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Failed call: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Retrying request: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Failed call: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Retrying request: Request{method=POST, url=http://localhost:55555/instantiate_bot, tags={class retrofit2.Invocation=za.co.entelect.challenge.network.BotServices.instantiateBot() [okhttp3.MultipartBody$Part@be35cd9]}}
Successfully instantiated bot: A - styphoiz on api port 55555
Config for player B : tournament-tmp/extracted/player-dfcdfc0c-a390-450b-83af-57d15d7ce91a/README.md
Exception during match execution
java.lang.Exception: Failed to find bot meta data from location: tournament-tmp/extracted/player-dfcdfc0c-a390-450b-83af-57d15d7ce91a/README.md
at za.co.entelect.challenge.config.BotMetaData.load(BotMetaData.java:86) ~[game-runner.jar:?]
at za.co.entelect.challenge.player.bootstrapper.PlayerBootstrapper.parsePlayer(PlayerBootstrapper.java:72) ~[game-runner.jar:?]
at za.co.entelect.challenge.player.bootstrapper.PlayerBootstrapper.loadPlayers(PlayerBootstrapper.java:50) ~[game-runner.jar:?]
at za.co.entelect.challenge.engine.bootstrapper.GameBootstrapper.run(GameBootstrapper.java:75) [game-runner.jar:?]
at za.co.entelect.challenge.engine.bootstrapper.GameBootstrapper.main(GameBootstrapper.java:55) [game-runner.jar:?]
Notifying of match failure
Creating zip: c9e9d2ee-ad90-4272-9d8e-15a6b36f2e08 for directory: ./match-logs

10

Yikes, that looks a tad more serious - but smell more like infrastructure hiccup than bot failure.

11

The match status seems to be funny as well, my bot threw out an exception and it showed the match status as successful unlike last year where it showed as requires attention.

1 Like
12

Yeah that doesn’t sound right at all.

13

Sweet, logs are now reflecting as under 10mb.

1 Like
14

Hi @styphoiz,

Yes the team managed to compress the logs :grinning:

3 Likes