Closed
Bug 1282789
Opened 9 years ago
Closed 9 years ago
Investigate why some files on s3 have a name ending with colon
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Assigned: whd)
Details
A job failure reported in bug 1282441 was caused by a filename ending with semicolon. We should investigate how that file was created with such a name.
Updated•9 years ago
|
Assignee: nobody → whd
Points: --- → 1
Priority: -- → P1
| Assignee | ||
Comment 1•9 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1282441#c4, deploying today.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•