Closed
Bug 1447632
Opened 8 years ago
Closed 8 years ago
Artifact builds on try server must contain accessible.tlb
Categories
(Firefox Build System :: General, enhancement)
Tracking
(firefox61 fixed)
RESOLVED
FIXED
mozilla61
| Tracking | Status | |
|---|---|---|
| firefox61 | --- | fixed |
People
(Reporter: MarcoZ, Assigned: MarcoZ)
Details
(Keywords: access)
Attachments
(1 file)
When creating try builds using artifact builds, accessible.tlb is not included in the resulting target.zip file. As a result, accessibility is not working properly when running such a build with a screen reader such as NVDA. if I just copy over an accessible.tlb from a regular nightly, it'll start to work. As an example of a try build with broken accessibility, see https://treeherder.mozilla.org/#/jobs?repo=try&revision=55523803881cb60675d1144da46d9e8170ce20b1
Comment 1•8 years ago
|
||
For reference, Accessible.tlb is generated in accessible/ipc/win/typelib. I'm not sure what's required to make this be considered an artifact for the purposes of artifact builds.
Comment 2•8 years ago
|
||
This should be easy to fix. Unfortunately the artifact build code currently has a list of file patterns that it uses to unpack a build into an objdir (which is separate from the list of things we use to package up the contents of dist/bin). The list for Windows builds is here:
https://dxr.mozilla.org/mozilla-central/rev/6ff60a083701d08c52702daf50f28e8f46ae3a1c/python/mozbuild/mozbuild/artifacts.py#421
| Comment hidden (mozreview-request) |
Comment 4•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8961060 [details]
Bug 1447632 - Make sure that TLB files are included in Windows artifact builds, .mielczarek
https://reviewboard.mozilla.org/r/229816/#review235598
Attachment #8961060 -
Flags: review?(ted) → review+
Pushed by mzehe@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9f270d21aef5
Make sure that TLB files are included in Windows artifact builds, r=ted.mielczarek
Comment 6•8 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Updated•7 years ago
|
Assignee: nobody → mzehe
You need to log in
before you can comment on or make changes to this bug.
Description
•