Add checks for invalid data in db

RESOLVED INCOMPLETE

Status

Release Engineering
General
P3
normal
RESOLVED INCOMPLETE
6 years ago
a month ago

People

(Reporter: catlee, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildbot][database])

(Reporter)

Description

6 years ago
Some windows machines freaked out and we ended up with properties like 
basedir 	2086735202 [sig] sh 1660 sig_dispatch_pending: Win32 error 298 releasing sigcatch_nosync(0xF8) 2086737081 [sig] sh 1660 sig_dispatch_pending: Win32 error 298 releasing sigcatch_nosync(0xF8) 2086737169 [sig] sh 1660 sig_dispatch_pending: Win32 error 298 releasing sigcatch_nosync(0xF8) 2086737259 [sig] sh 1660 sig_dispatch_pending: Win32 error 298 releasing sigcatch_nosync(0xF8) 2086737290 [sig] sh 1660 sig_dispatch_pending: Win32 error 298 releasing sigcatch_nosync(0xF8) 2086737378 [sig] sh 1660 .. [property value too long]

in the database. These weren't stored as valid json, and so our db export script (postrun.py) was choking on them.

maybe we should have nagios checks for invalid data in the db, or make postrun.py more resilient to bad data.
(Reporter)

Updated

6 years ago
Priority: -- → P3
Whiteboard: [buildbot][database]
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Updated

a year ago
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

a month ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.