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

alphagov / backdrop / 2502
91%
master: 89%

Build:
Build:
LAST BUILD BRANCH: upgrade_paas_stack
DEFAULT BRANCH: master
Ran 28 Oct 2015 11:13AM UTC
Jobs 1
Files 56
Run time 8s
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
2502

push

travis-ci

leenagupte
Format timestamp before creating id field

Slight differences in the way the _timestamp cell is formatted (in
file uploads) results in duplicated data in the dataset.

What’s happening is this: _timestamp is listed as an auto_id for
the data set. All auto_id fields and values are joined together and
then base64 encoded and stored in the _id field.

AFTER the _id field has been created for the data record, the
_timestamp is parsed and converted to utc format. This means that
the date format of the timestamp can differ from the date format of
the timestamp in the _id.

The _id is used as a unique key for the data set.
The same _timestamp with a different date format will generate a
different _id value and will added as a new row in backdrop.

The fix was just to move converting the _timestamp to utc format
to BEFORE the base64 encoded _id is generated.

1906 of 2103 relevant lines covered (90.63%)

0.91 hits per line

Jobs
ID Job ID Ran Files Coverage
1 2502.1 (SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='' NO_AUTOPEP8=1) 28 Oct 2015 11:13AM UTC 0
90.63
Travis Job 2502.1
Source Files on build 2502
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #2502
  • b43cd5aa on github
  • Prev Build on only-allow-utc-timestamp-in-ids (#2500)
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