Skip to content

Corrupt binary log in some circumstances #2990

Open
@rainersigwald

Description

@rainersigwald

The build in question is Microsoft-internal, so I can't share the .binlog file, but I am in possession of a binary log file that appears to have been generated badly.

s:\msbuild>msbuild /flp:v=d /noconlog S:\VS\src\xmake\msbuild_ddbld572.binlog
Microsoft (R) Build Engine version 15.6.76.11871 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

There was an exception while reading the log file: Parameter "BuildEventContext" cannot be null.
s:\msbuild>msbuild /flp:errorsonly;logfile=msbuild.err2 /noconlog S:\VS\src\xmake\msbuild_ddbld572.binlog
Microsoft (R) Build Engine version 15.6.76.11871 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

There was an exception while reading the log file: BinaryReader encountered an invalid string length of -1053630578 characters.

It appears to be safe to ignore the BuildEventContext part (and just skip message events with no message or context), but the latter is fatal as far as I can tell.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bot-excludeBots should explicitly ignore this issue/PRneeds-more-infoIssues that need more info to continue investigation.triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions