"Cannot lock ref" error on Travis CI job about webref HOT 3 CLOSED

Was there another Travis CI job running around the same time, like if two of them got queued up? I'm thinking this sort of thing could happen if two jobs try to push the same branch at the same time.

from webref.

That is what I thought too, but jobs typically run 6 hours apart, so that did not make sense... until yesterday when your comment made me realize that Travis CI was actually enabled twice in the repo settings: with a webhook, and at the organization level. Each push to master actually triggered two Travis CI jobs in parallel (one under travis-ci.org and another one under travis-ci.com) as a result.

So, problem solved, I deleted the webhook :)

from webref.

Aha, that would also explain the confusion in #58 :)

from webref.