Observing occasional strings of IsolatedError: Failed to parse (No JSON object could be decoded) |
||
Issue descriptionhttps://chromium-swarm.appspot.com/task?id=42659ec52f7ded10&refresh=10&show_raw=1 5259 2019-01-14 14:41:24.701 E: Failed to parse .isolated file: 5259 2019-01-14 14:41:24.703 E: internal failure: Failed to parse (No JSON object could be decoded): ... Traceback (most recent call last): File "/b/s/swarming_bot.1.zip/client/run_isolated.py", line 734, in map_and_run use_symlinks=data.use_symlinks) File "/b/s/swarming_bot.1.zip/client/run_isolated.py", line 531, in fetch_and_map use_symlinks=use_symlinks) File "/b/s/swarming_bot.1.zip/client/isolateserver.py", line 1266, in fetch_isolated bundle.fetch(fetch_queue, isolated_hash, algo) File "/b/s/swarming_bot.1.zip/client/isolateserver.py", line 1141, in fetch item.load(f.read()) File "/b/s/swarming_bot.1.zip/client/isolated_format.py", line 100, in load self.data = load_isolated(content, self.algo) File "/b/s/swarming_bot.1.zip/client/isolated_format.py", line 403, in load_isolated raise IsolatedError('Failed to parse (%s): %s...' % (v, content[:100])) IsolatedError: Failed to parse (No JSON object could be decoded): ... Failed to parse (No JSON object could be decoded): ... Results in immediate BOT_DIED
,
Jan 14
problem persists after reboot
,
Jan 14
https://isolateserver.appspot.com/browse?namespace=default-gzip&hash=e9e4b5010008ed9361f51726d743f3f967689af0 and its includes look good. Maybe a corrupted cache on the bot? I'd recommend to rm -rf /b/s/isolated_cache and restart it. Cache verification on startup is somewhere in the roadmap.
,
Jan 15
remediation attempted from #c3 Will let you know how it fairs |
||
►
Sign in to add a comment |
||
Comment 1 by kjlubick@google.com
, Jan 14Status: Assigned (was: Untriaged)