Taskcluster log has invalid buildbot-style results status code of "255"

RESOLVED INCOMPLETE

Status

Taskcluster
Platform and Services
RESOLVED INCOMPLETE
3 years ago
4 months ago

People

(Reporter: emorley, Unassigned)

Tracking

Details

(Reporter)

Description

3 years ago
In this log:
https://s3-us-west-2.amazonaws.com/taskcluster-public-artifacts/TX47pxP4SEGTtdzWfHWgYg/0/public/logs/live_backing.log

There's the line:

========= Finished Running tests (results: 255, elapsed: 819 secs) (at 2015-08-10 16:11:17.752336) =========

A results code of "255" isn't valid, and so causes Treeherder to display that step as status "unknown" in the log viewer.

The "results" property is not exit code, it's an (awful) mapping of job states, see:
https://github.com/mozilla/treeherder/blob/5ae5c4909d183f0f7d6c7c0dc31c2afe6e03b876/treeherder/etl/buildbot.py#L7-L15

Given the job seemed to have infra problems, I would have expected a "result" of say "4".
(Reporter)

Updated

3 years ago
Summary: Taskcluster logs have invalid buildbot-style results status line → Taskcluster log has invalid buildbot-style results status code of "255"
Component: Integration → Platform and Services
(Reporter)

Comment 1

4 months ago
Mass-closing old bugs I filed that have not had recent activity/no longer affect me.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.