If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Buildbot is not producing warnings in some of the buildsteps when it should

VERIFIED FIXED

Status

Tamarin
Build Config
VERIFIED FIXED
9 years ago
9 years ago

People

(Reporter: Brent Baker, Assigned: Brent Baker)

Tracking

Details

Attachments

(2 attachments)

(Assignee)

Description

9 years ago
1) The "file-check" buildstep which checks line-endings and MPL license compliance is no longer producing buildbot warnings when it finds an issue.

2) The "size-report" should produce a warning if there are new objects that are found that are not classified in the utils/modules.txt
(Assignee)

Comment 1

9 years ago
Created attachment 377160 [details] [diff] [review]
file-check patch

This patch makes sure that warnings produced the buildsteps by echoing "buildbot_status: SUCCESS | FAILURE | WARNINGS" are picked up by buildbot
Assignee: nobody → brbaker
Attachment #377160 - Flags: review?(dschaffe)
(Assignee)

Comment 2

9 years ago
Created attachment 377165 [details] [diff] [review]
size-report patch

If we find uncategorized files in the "sizereport" script then produce a buildbot warning. Currently looking for *.obj and *.dll files
Attachment #377165 - Flags: review?(dschaffe)
(Assignee)

Updated

9 years ago
Status: NEW → ASSIGNED

Updated

9 years ago
Attachment #377160 - Flags: review?(dschaffe) → review+

Updated

9 years ago
Attachment #377165 - Flags: review?(dschaffe) → review+
(Assignee)

Comment 3

9 years ago
changeset:   1883:83505debc2b4
tag:         tip
user:        Brent Baker <brbaker@adobe.com>
date:        Thu May 14 09:48:31 2009 -0400
description:
Bug 492750: fix the file-check buildstep to produce buildbot warnings
- update sizereport buildstep to produce a warning if unclassified objects are in the map
(r=dschaffe)
(Assignee)

Updated

9 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Assignee)

Updated

9 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.