Work around a Perforce error regression in p4python 2024.1.2625398.

Review Request #14080 — Created Aug. 8, 2024 and submitted — Latest diff uploaded

Information

Review Board
release-7.x

Reviewers

The recently-released p4python 2024.1.2625398 changed error handling to
separate out errors, warnings, and raw results. During __str__, it
prioritizes errors, then warnings, and then the raw value, depending on
what state is available. Unfortunately, they don't always set each of
these in the constructor, leading to AttributeErrors being raised.

We now check for this and fall back to grabbing the raw value, which is
what we were implicitly checking in prior releases.

Unit tests pass with the new build of p4python.

Commits

Files