Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Collection of container console logs from Helix jobs fails sometimes

See original GitHub issue

Context

When collecting logs from within the Docker container after Helix job is finished, it can sometimes fail, possibly due to encoding problems.

The collection happens here: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines?path=/resources/helix-scripts/helix/dockerhelper.py&version=GBmain&line=197&lineEnd=198&lineStartColumn=1&lineEndColumn=77&lineStyle=plain&_a=contents

Example

The test log would be empty (example) and run.py log would have this log line:

2023-04-27T21:33:17.208Z    ERROR      executor(733)    _execute_command_in_container    Exception: 'charmap' codec can't encode characters in position 70671-70672: character maps to <undefined>

Release Note Description

Make log processing more forgiving to UTF8 encoding errors

Issue Analytics

State:
Created 5 months ago
Comments:12 (12 by maintainers)

Top GitHub Comments

1reaction

pavelsavaracommented, Apr 28, 2023

It likely fails on .decode("utf-8")

0reactions

pavelsavaracommented, Jul 29, 2023

PR merged

Top Results From Across the Web

Job types - Documentation for Helix Control-M 21 API

The default for PostCommands is false, that is, the job will complete successfully even if any post-command fails.

22.1 enhancements and patches - BMC Documentation

The following BMC Helix ITSM data is not archived: BMC Requester console records; Foundation data (for example, organizations and locations); Process setup data ......

Helix Core Server Administrator Guide

All p4d error and info logs are in UTF8 for a server in unicode mode. You need an UTF8 console or editor to...

Troubleshooting GitLab Runner

Job failed (system failure): preparing environment: This error is often due to your shell loading your profile, and one of the scripts is...

Container killed while running / Output logs missing in ...

Summary. The job output is not completely displayed in GitLab console. That happened for successful and failed jobs.