Closed rsimha closed 7 years ago
Here's an example of the warning we're seeing. Note that all our logs are silenced, and the only ones being printed are by Percy.
https://travis-ci.org/ampproject/amphtml/jobs/257300515#L649
/cc @fotinakis @timhaines
This logging really comes from our percy-client gem. The logging is resolved if we switch the order of these two lines.
However, that breaks this test which I haven't been able to figure out just now. We'll work on this @rsimha-amp.
@rsimha-amp This should be resolved now with the release of percy-client 1.13.5. If you update your gem bundle and still see issues with this, please let me know.
Cool, will do. Thanks!
I just checked our logs, and the errors are gone. Thanks for the fix.
This started recently, presumably due to
faraday
receiving a version bump.See https://github.com/percy/percy-capybara/blob/68a6dc2257dad18d1237c3c9772c1ee073e206d0/percy-capybara.gemspec#L31