search

spmeesseman / svn-scm-ext

MIT License
1 stars 4 forks source link

An in-range update of vscode-test is breaking the build 🚨 #27

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency vscode-test was updated from 1.3.0 to 1.4.0.

🚨 View failing branch.

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

vscode-test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **spmeesseman.svn-scm-ext:** [1 errors / 9 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (Windows CodeInssiders):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (Windows CodeCurrent):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (Windows Code26):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (macOS CodeInssiders):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ❌ **spmeesseman.svn-scm-ext (Linux CodeInssiders):** [1 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (macOS CodeCurrent):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (Linux CodeCurrent):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (macOS Code26):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521) - ✅ **spmeesseman.svn-scm-ext (Linux Code26):** [0 errors / 1 warnings](https://dev.azure.com/spmeesseman/03529c36-5d5a-4a68-8ddb-b7b38d8e70b2/_build/results?buildId=1521)
Commits

The new version differs by 6 commits.

  • 9aade08 v1.4.0
  • b4fa3ac Update readme
  • b045101 Changelog for #56
  • 5f6c7d5 Merge pull request #56 from jcreedcmu/jcreed/signal
  • a988982 runTests: propagate signal when subprocess terminated
  • 03e1f9b Update azure-pipelines.yml for Azure Pipelines

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 4 years ago

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