• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

wikimedia / parsoid / 2265
85%

Build:
DEFAULT BRANCH: master
Ran 01 Feb 2019 10:52PM UTC
Jobs 3
Files 116
Run time 7min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
2265

push

travis-ci

arlolra
Add media info in a post-processing pass

The basic idea here is to generate the media structure in the token
stream using a stuffed span with a redlink, as in T169975, and
augmenting the nodes on the DOM once the media info has been fetched.

A redlink is justified as the canonical representation of the media
elements before info is fetched because it's the fallback if fetching
fails and the media type is unknown until the info is retrieved.

Most options are stored in data-mw until the media type is fetched and
it's determined that they're applicable.  This is a bit of a reversion
of how things were done before where inapplicable options were removed
post-facto.

For consistency and styling's sake, figcaptions are now always added to
block figures.

The pass has to be run before generating headings anchor, since that
depends on the text content (ie. redlinks).  This rearranges things in
the post-processor and adds another pass.

The post-processing pass to add media info is run on subpipelines as
well as the top level so that the media info is present in cases where
we embed HTML in data-mw (which is currently skipped by the top level
only passes, except for the cite extension, which has special handling,
see T214994) and to avoid an additional post-processing pass for the
gallery extension, which scales media of packed galleries.  This comes
at the cost of making additional queries for each pipeline and requires
the add media pass to be idempotent.

Filed T214241 for figuring out what to do about data-mw info being
clobbered by template annotations.

The newly failing blacklisted tests are from roundtripping media options
in galleries, which requires a general refactor for support.  See the
FIXMEs added there.

Performance should be expected to regress by the amount of work we're
able to overlap in the async phase of the pipeline while the media info
is being fetched.  Considering a lot of that work is caught up waiting
for the batch to return (oth... (continued)

9396 of 11810 branches covered (79.56%)

14821 of 17571 relevant lines covered (84.35%)

80732.54 hits per line

Jobs
ID Job ID Ran Files Coverage
1 2265.1 01 Feb 2019 10:59PM UTC 0
84.35
Travis Job 2265.1
2 2265.2 01 Feb 2019 10:52PM UTC 0
84.35
Travis Job 2265.2
3 2265.3 01 Feb 2019 11:00PM UTC 0
84.35
Travis Job 2265.3
Source Files on build 2265
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #2265
  • 3a0dff6a on github
  • Prev Build on master (#2264)
  • Next Build on master (#2266)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc