search

DBCDK / dk5

DK5 Digital
GNU Affero General Public License v3.0
0 stars 0 forks source link

An in-range update of newrelic is breaking the build 🚨 #668

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency newrelic was updated from 4.12.0 to 4.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

newrelic is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/DBCDK/tanterne/builds/470778212?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 131 commits.

  • 0dc2a65 release: published 4.13.0
  • 93ab674 formatting changelog
  • c042419 Updated changelog for v4.13.0.
  • d9cb1a7 Merge pull request #1646 from NodeJS-agent/mgoin/NODE-1955-ResponseHandlingCrossAgentTests
  • 8f1f85c Fixes stopping of automatically scheduled harvests for response code tests.
  • e10476a Simplifies loading of json for test cases. Adds variable initialization and removes redundant autoend calls.
  • 55ff92e Bumps tap integration test per-file timeout to 2 minutes from 30 seconds.
  • 588461f Fixes state check as agent will now go from starting to connecting
  • a702136 Restructures response handling tests.
  • cbf1a2c Makes easier to add/remove endpoints from response code tests.
  • 8b709ec Adds sql_trace_data to response handling tests.
  • f797f60 Adds span_event_data and custom_event_data to response handling tests.
  • bcc1eb5 Adds transaction_sample_data to response handling tests.
  • 0ed5670 Adds error_data and analytic_event_data to response handling tests.
  • d4a36dc Adds error_event_data to response handling tests.

There are 131 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 4.12.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.