Skip to content

Conversation

@rafatower
Copy link

This test fails a bit randomly, at least in travis. A description
of the assertion helps to understand what's going on.

This test fails a bit randomly, at least in travis. A description
of the assertion helps to understand what's going on.
@rafatower rafatower force-pushed the add-assertion-message branch from 6e863d6 to a05bfc1 Compare January 9, 2018 09:25
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 6e863d6 on CartoDB:add-assertion-message into ** on mapbox:master**.

@rafatower
Copy link
Author

I'd personally remove those 2 assertions and keep benchmarks separately.

My 2 cents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants