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

boostorg / unordered / 128 / 3
0%
develop: 0%

Build:
DEFAULT BRANCH: develop
Ran 01 May 2017 09:42PM UTC
Files 8
Run time 0s
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

01 May 2017 09:16PM UTC coverage: 0.0%. Remained the same
label="gcc 32 bit C++11"; user_config="using gcc : : g++-4.8 -m32 -fsanitize=address -Werror --std=c++11 ;"

push

travis-ci

danieljames
Use the unordered container for the fake merge in merge test

The merge tests into containers with unique keys are failing on some
platforms. My guess is that because of differences between ordering of
nodes with equivalent keys that different nodes are being 'merged' in
the unordered containers and the tracker containers. So when creating
the fake merge, use the unordered container as a reference. This is a
little less pure, but should be a good enough test.

0 of 0 relevant lines covered (NaN%)

0.0 hits per line

Source Files on job 128.3 (label="gcc 32 bit C++11"; user_config="using gcc : : g++-4.8 -m32 -fsanitize=address -Werror --std=c++11 ;" )
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 128
  • Travis Job 128.3
  • d84a5744 on github
  • Prev Job for label="gcc 32 bit C++11"; user_config="using gcc : : g++-4.8 -m32 -fsanitize=address -Werror --std=c++11 ;" on develop (#127.3)
  • Next Job for label="gcc 32 bit C++11"; user_config="using gcc : : g++-4.8 -m32 -fsanitize=address -Werror --std=c++11 ;" on develop (#129.3)
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