Open dcrissman opened 9 years ago
I found a couple complaints about a similar sounding issue from others, in both cases they decided to abandon 1.8.7 altogether.
Talked with @dcrissman and we're going to recommend removing ruby 1.8.7 from our builds for now (PR coming soon). Our puppet runs internally are not having problems. Tagging this issue for the Bill release.
We started getting this rather obscure error message on on PRs. I then re-ran the master branch which had previously been all green lights, but then started getting this same error there too. Only seems to be an issue for ruby 1.8.7.