Contribute to Open Source. Search issue labels to find the right project for you!

Decide on whether to test update action during CI run

samsung-cnct/k2cli

<!– Thanks for filing an issue! Before hitting the button, please answer these questions.–>

Is this a BUG REPORT or FEATURE REQUEST?: feature request, but more of a research/decision issue

<!– If this is a BUG REPORT, please: - Fill in as much of the template below as you can. If you leave out information, we can’t help you as well.

If this is a FEATURE REQUEST, please: - Describe in detail the feature/behavior/change you’d like to see.

In both cases, be ready for followup questions, and please respond in a timely manner. If we can’t reproduce a bug or think a feature already exists, we might close your issue. If we’re wrong, PLEASE feel free to reopen it and explain why. –>

K2cli has the ability to update nodes per the update action. Should we test this during CI?

Pros: It is a feature we offer; we should test it. Cons: It can take a very long time to test this action (roughly ten minutes per node being updated). As well, since update happens via a change in the config file, CI needs a way to alter its own config file.

Updated 17/08/2017 20:05

Add junit to CI

samsung-cnct/k2cli

<!– Thanks for filing an issue! Before hitting the button, please answer these questions.–>

Is this a BUG REPORT or FEATURE REQUEST? feature request <!– If this is a BUG REPORT, please: - Fill in as much of the template below as you can. If you leave out information, we can’t help you as well.

If this is a FEATURE REQUEST, please: - Describe in detail the feature/behavior/change you’d like to see.

In both cases, be ready for followup questions, and please respond in a timely manner. If we can’t reproduce a bug or think a feature already exists, we might close your issue. If we’re wrong, PLEASE feel free to reopen it and explain why. –>

k2cli version (use k2cli version): Current version (1.08)

Environment: I’m not sure what this means.

What happened: Creating the first CI run for k2cli, we tried to add junit to the test run. This ultimately caused some of the unit tests in the project to fail, with no error message in the output.

What you expected to happen: The tests should have passed.

How to reproduce it (as minimally and precisely as possible): Add junit as per PR #104 in some of the earlier commits; watch Jenkins report an unstable build.

Updated 17/08/2017 20:04

Travis build hangs for 10min -> build aborted

stomp-php/stomp-php

I can see several builds halting at the very same unit test, across different php versions. feels like a race condition somewhere..

I guess its the same unit test, because of “same number of dots” in the phpunit progress bar

$TRAVIS_BUILD_DIR/vendor/bin/phpunit

PHPUnit 4.8.36 by Sebastian Bergmann and contributors.

Warning:    The Xdebug extension is not loaded

        No code coverage will be generated.

................
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

occurred on e.g. https://github.com/stomp-php/stomp-php/pull/77/commits/24ececda31f5255fcaac02bcf5e8a928693bfd0b

https://travis-ci.org/stomp-php/stomp-php/jobs/265151314 https://travis-ci.org/stomp-php/stomp-php/jobs/265151316

Updated 19/08/2017 06:47 9 Comments

ensure all-but-e2e correctly sets failure notification in github

samsung-cnct/k2

the all-but-e2e notification will only fire if the cluster comes all the way up correctly and comes all the way down correctly. this doesn’t always happen. we are left with a required notification this is pending and two notifications that have failed. we have sufficient information to know that the CI run failed but it would be best if the required CI notification wasn’t pending.

Updated 14/08/2017 23:44

kubernetes 1.8 support

samsung-cnct/k2

k8s v1.8.0-alpha2 has been released (CHANGELOG)[https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md#v180-alpha2] we should start testing against this version to make sure we are ready to go when it is released. We can also help the project by filing issues against kubernetes itself.

Updated 09/08/2017 20:42 1 Comments

Travis skips some tests

Wangscape/Wangscape

Here are the test logs from AppVeyor and Travis for PR #158: * https://ci.appveyor.com/project/serin-delaunay/wangscape/build/0.1.239#L1772 * https://travis-ci.org/Wangscape/Wangscape/jobs/260838067#L776

Appveyor runs 156 tests from 64 test cases, and Travis runs 146 tests from 60 cases. The missing test cases are TestBitmap (new in the PR), TestCalculatorLinear, TestRasterImage, and TestRasterValues.

Travis was previously configured to skip some tests that required OpenGL functions, but that argument was removed and none of these test cases would have been affected.

Updated 04/08/2017 09:36

Update travis CI jobs to use trusty

github/octocatalog-diff

Reference: https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming

Presently at least 2 of our 5 builds have trouble running under trusty:

https://travis-ci.org/github/octocatalog-diff/builds/259510369

Generally complaining, when things shell out, about something like:

/home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/site_ruby/2.2.0/rubygems.rb:270:in `find_spec_for_exe': can't find gem bundler (>= 0.a) (Gem::GemNotFoundException)
Updated 31/07/2017 21:45

Helm charts deployment should merge a new release into an existing index.yaml

samsung-cnct/k2-charts

TL;DR

Expected behaviour: * New versions of charts must be added to index.yaml file. The index.yaml file should contain metadata to all versions of the charts.

Actual behaviour: * Only 1 version of each chart exist in the index.yaml file. The old archives are still there, but not reachable by helm as the metadata is missing from index.yaml.

Description

Yesterday, I tried deploying the central-logging chart on our k8s cluster, but if failed. The published central-logging chart archive does not contain the archives of it’s dependencies.

I suspect the release process does not contain a helm dependency update command when the chart version is packaged.

To circumvent that, I cloned this Git repo and ran helm dependency update myself. If failed because the metadata for daemon-fluentd 0.2.0 is missing from the index.yaml file.

I had to bump the version in the requirements.yaml for the dependency update to succeed.

Updated 02/08/2017 21:03 2 Comments

RFC: Caching on CI machine

FStarLang/FStar

Our CI takes roughly 12 minutes to run, with approx 2 minutes spent bootstrapping and 10 spent verifying examples. Here’s a proposal to make it better:

  • Every time we send a query to Z3 and get unsat, we record a hash of that query in a cache file.
  • Every time we get a new VC, we check whether we already know that it’s unsat from the cache file.

The cache file should also include a Z3 version, and it should survive across CI invocations.

The idea is that in the relatively common case in which a change to F* changes few VCs, we can skip most of the 10 minutes currently spent reverifying everything.

Thoughts?

Updated 19/07/2017 16:51 5 Comments

Older platforms require Filetree meta data files or newer Metacello version

SeasideSt/Seaside

Travis builds for older versions fail if certain meta data files are missing. The solution is to force the use of the latest Metacello version (which is trivial with smalltalkCI). However, I’m not sure whether we can expect users of older platforms to suddenly require a newer version of Metacello.

This will certainly hit us when we start using Iceberg fully, as Iceberg does not write meta data files. If we still want to go that way, which I think we should, we need to decide, whether we can start now and require older platforms to load a newer Metacello version, or whether we want to have a release with a clean transition (we could simply say that it will be 3.3).

If we decide to wait, then I will have to redo my PR’s as they are missing meta data files. @jbrichau @marschall please comment.

Updated 24/07/2017 05:12 9 Comments

restructure Dockerfile

samsung-cnct/k2

The Dockerfile currently needs to always be built with --no-cache as the only image layers that will change are the k2-tools FROM layer and the output of a RUN command. This means that if we are building the same tag, say, latest, repeatedly we will only push a new version of the K2 image when k2-tools changes.

I am unsure if the Dockerfile should be checking out a fresh version of the source code or if it should be using the repo it is a part of. Probably the latter but some thought should be put into this. And a Makefile.

Updated 26/07/2017 20:34

Submit application to F-Droid

flyve-mdm/flyve-mdm-android-inventory-agent

Hi, @rafaelje

Could you follow these steps to submit the application to F-Droid?

Template to discuss the inclusion on F-Droid

  • [x] The app complies with the inclusion citeria
  • [x] The app is not already listed in the repo or issue tracker.
  • [x] The original app author has been notified (and supports the inclusion).

Link to the source code:

https://github.com/flyve-mdm/flyve-mdm-android-inventory-agent

Link to app in another app store:

https://play.google.com/store/apps/details?id=org.flyve.inventory.agent

License used:

GPLv3

Category:

Summary:

Description:

Flyve MDM is an open source mobile device management software (SaaS), that enables you to secure and manage all the mobile devices of your business via a unique web-based console (MDM). Our app makes IT Administrators daily life much easier! It offers them a wide range of enhanced functions, to efficiently manage the entire mobile fleet of the company in just a few clicks.


Related links: - https://f-droid.org/contribute/ - https://forum.f-droid.org/ - https://f-droid.org/forums/forum/submission-queue/ - https://f-droid.org/wiki/page/Inclusion_Policy - https://f-droid.org/manual/

Updated 18/08/2017 12:08

do we need to specify a kubernetes version for GKE

samsung-cnct/k2

When GKE creates a cluster, GKE will always create the cluster at its default version no matter what you tell Deployment Manager (google product). GKE will then perform a rolling update of all nodes so they match the target version. This takes ~45 minutes for default clusters.

We are currently checking the status of this weekly so the K2 default version lines up with the GKE default version. If its possible, we would prefer to not do this. It has been suggested that we can specify no Kubernetes version and GKE will give us the (fast) default version. If so, we should do that for GKE.

Updated 03/08/2017 17:49 1 Comments

Fix beta/canary

ember-intl/ember-intl

3 tests are failing, need to investigate why.

not ok 92 PhantomJS 2.1 - format-message: should respect format options for date ICU block
    ---
        actual: >
            false
        expected: >
            true
        stack: >
            exception@http://localhost:7357/assets/test-support.js:8165:46
            adapterDispatch@http://localhost:7357/assets/vendor.js:55181:22
            dispatchError@http://localhost:7357/assets/vendor.js:37192:23
            invokeWithOnError@http://localhost:7357/assets/vendor.js:19935:24
            flush@http://localhost:7357/assets/vendor.js:19803:27
            flush@http://localhost:7357/assets/vendor.js:19994:36
            end@http://localhost:7357/assets/vendor.js:20102:47
            run@http://localhost:7357/assets/vendor.js:20180:29
            run$1@http://localhost:7357/assets/vendor.js:37553:32
            render@http://localhost:7357/assets/test-support.js:9267:27
            http://localhost:7357/assets/tests.js:788:16
            runTest@http://localhost:7357/assets/test-support.js:4028:34
            run@http://localhost:7357/assets/test-support.js:4014:13
            http://localhost:7357/assets/test-support.js:4220:15
            advance@http://localhost:7357/assets/test-support.js:3673:26
            begin@http://localhost:7357/assets/test-support.js:5485:27
            http://localhost:7357/assets/test-support.js:4599:11
        message: >
            TypeError: undefined is not a constructor (evaluating 'references[i].value()')

https://travis-ci.org/ember-intl/ember-intl/jobs/252683262

Updated 12/07/2017 06:12

Add build retries to Zeebe CI build

zeebe-io/zeebe

At the moment the Zeebe build still contains unreliable test cases and often fails with the same error. Or dies while running the test suite. Therefore we could add a retry plugin to Jenkins (i.e. Naginator) and configure it to retry a failed Zeebe build 3 times.

Updated 04/07/2017 06:02

Add https://github.com/prettier/eslint-config-prettier to avoid future conflicts in eslint rules

yarnpkg/yarn

Do you want to request a feature or report a bug? Feature

What is the current behavior? If we add an eslint rules that conflicts with prettier we need to turn off it.

What is the expected behavior? Add https://github.com/prettier/eslint-config-prettier and forget about that :D When I tried the cli tool prettier/eslint-config-prettier#cli-helper-tool there are some problems: every yarn command put yarn run v<version> on top of the result of each command.. when I try to pipe with eslint-config-prettier-check it does not work as expected.

Just for info after adding https://github.com/prettier/eslint-config-prettier, i run it:

yarn run --json eslint -- --print-config .eslintrc | yarn run eslint-config-prettier-check

and the response is: Failed to parse JSON: Unexpected token { in JSON at position 120 error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command

because when I type

yarn run --json eslint -- --print-config .eslintrc

this is the result:

{"type":"command","data":"\"/Users/user/Projects/open-source/yarn/node_modules/.bin/eslint\" --print-config .eslintrc"}
{
  "globals": {
    "Array": false,
    "ArrayBuffer": false,
    "Boolean": false,
...
}

Please mention your node.js, yarn and operating system version. Every version of yarn

Maybe this issue is trivial because I forget about one flag that can turn off the head.

Updated 04/07/2017 06:21

Add JDK 9 build to CI

zeebe-io/zeebe

It would be interesting to monitor the if there are any upcoming problems with JDK 9. Therefore we need a JDK 9 build for every Zeebe project.

Updated 03/07/2017 12:26 1 Comments

Run integration tests on Windows

zeebe-io/zeebe
  • Run the integration tests on Windows 7 or 10 on Jenkins

Windows is a supported environment in the sense that our users can expect to run Zeebe successfully in it.

More urgently, we have a regression with deletion of temp files that went unnoticed.

Updated 30/06/2017 13:19

Add spell checker to CI

necx-org/nodes

Continuous integration should do spell checking. Consider a glossary of nuclear terms. Don’t require perfect spelling (probably impossible to get the full list of acceptable nuclear terms in the glossary). Just report bad spelling.

Updated 29/06/2017 14:10

Set up CI

necx-org/nodes

CI needs to do a ton of things eventually (see below). For now, set up a CI instance for this repository so that the things below (each with their own issue) can be implemented eventually.

  • Testing
    • Metadata checker
    • Dependency tree logic
    • Splle c hkjser
    • Pep8 checker
    • LaTeX build checker
  • Deployment
    • Build jekyll website
    • Build d3.js dependency graph
Updated 29/06/2017 14:05

Test fixtures are huge

yarnpkg/yarn

The __tests__/fixtures/ is around 80MB. The files which take most of the space are the .tgz.bin files which I assume are regenerable.

(If you also agree that this is a problem, then) a solution to this could be adding a pretest script to download these files.

Updated 28/06/2017 22:06 3 Comments

Cypress hangs if spec file is outside the integration folder

cypress-io/cypress
  • Operating System: Mac
  • Cypress Version: 0.19.4
  • Browser/Browser Version: built-in electron browser

Are you requesting a feature or reporting a bug?

reporting a bug

Current behavior:

I made a repo with the setup: https://github.com/bahmutov/test-moved-cypress-spec

I put the spec file a-spec.js NOT in the cypress/integration folder (which is empty) but in the root of the repo. When running the test from the command line Cypress hangs

command json { "scripts": { "test": "cypress run --spec a-spec.js" } } ``` $ npm test

test-moved-cypress-spec@1.0.0 test /Users/irinakous/git/test-cypress-module cypress run –spec a-spec.js

⧖ Verifying Cypress executable… ! Installed version (0.19.4) does not match package version (0.20.0-dev.20170620.121030)

✓ Successfully verified Cypress executable

Started video recording: /Users/irinakous/git/test-cypress-module/cypress/videos/jfmrg.mp4

(Tests Starting) ^C ```

I can show the browser window with the UI error

$ ./node_modules/cypress/dist/Cypress.app/Contents/MacOS/Cypress --project $PWD --spec a-spec.js --show-headless-gui

screen shot 2017-06-21 at 8 52 17 am

First, the spec file fails to load (I would expect that) http://localhost:58231/__cypress/a-spec.js 404 (Not Found)

The JavaScript error Unhandled rejection TypeError: Cannot read property 'options' of null at $Cypress.window.$Cypress.$Cypress.initialize (http://localhost:58231/__cypress/static/js/cypress.js:40:19) at Object.run (http://localhost:58231/__cypress/runner/runner.js:63116:12) at http://localhost:58231/__cypress/runner/runner.js:62179:32

In the expression this.mocha and this.runner are null js $Cypress.prototype.initialize = function(specWindow, $remoteIframe) { this.mocha.options(this.runner);

Expected behavior:

  • [ ] the error should be shown in the UI in this case, not just in the DevTools console.
  • [ ] the error should be shown in the terminal when running in the headless mode and the run should exit with error code

How to reproduce the current behavior:

Clone the repo git@github.com:bahmutov/test-moved-cypress-spec.git and execute npm it to recreate the run. Use the command above to show the GUI during the run

Test code:

describe('cypress example', () => {
  it('works', () => {
    expect(true).to.be.true()
  })
})

Additional Info (images, notes, stack traces, etc)

Updated 21/06/2017 12:59

Increase devices in travis testing

MobileApplicationsClub/ARD

Reason - Currently we are only testing api 21 for all our tests. But we need to add checking for api up to 25

Also we need to test the app for devices of various screen sizes as many UI components may not be visible in certain devices

I would suggest to use matrix in travis https://docs.travis-ci.com/user/speeding-up-the-build/

Updated 29/06/2017 13:04 1 Comments

Setup Continuous Integration and change how we git

ZencashOfficial/zen

Botio is a great lightweight opensource CI used with z-classic/zclassic z-classic/z-nomp and our website, and I recommend we use it again for zen.

We can use a script to auto package eleos for release whenever a commit is pushed to master. To make sure we don’t have 200+ eleos releases every month, we we should push commits into branch development instead. Whenever we are ready for release, pull into master and have botio package eleos.

Updated 17/07/2017 01:26 5 Comments

Trigger CI build when dependency is updated

tue-robotics/tue_robocup

Can be done perhaps via http://eng.rightscale.com/2015/04/27/dependent-builds-in-travis.html or https://github.com/mernst/plume-lib/blob/master/bin/trigger-travis.sh i.e. the dependencies trigger a build of it’s dependents.

To determine at least some dependencies, we might use rospack depends-on

Updated 20/06/2017 10:15 3 Comments

Add CI

raxod502/radian

By this point, there are a number of ways I can accidentally drop the ball on my Emacs config and push something stupid:

  • forget to test that a deferred installation actually works
  • forget to freeze my package versions
  • forget to validate my el-patches
  • fail to notice that Emacs errors out on startup (yes, really)

This stuff should be tested by Travis so I can’t get away with it.

Updated 17/07/2017 03:33 2 Comments

Building Artifactory container for Pineapple CI setup fails with NullPointerException

athrane/pineapple

com.alpha.pineapple.plugin.PluginExecutionFailedException: Operation failed with exception: java.lang.NullPointerException. Operation execution is aborted. at com.alpha.pineapple.plugin.docker.operation.DeployConfiguration.execute(DeployConfiguration.java:134) at com.alpha.pineapple.plugin.session.RetrySessionHandlerImpl.execute(RetrySessionHandlerImpl.java:123) at com.alpha.pineapple.command.InvokePluginsCommand.excuteWithPlugin(InvokePluginsCommand.java:399) at com.alpha.pineapple.command.InvokePluginsCommand.executeModel(InvokePluginsCommand.java:355) at com.alpha.pineapple.command.InvokePluginsCommand.executeModels(InvokePluginsCommand.java:270) at com.alpha.pineapple.command.InvokePluginsCommand.execute(InvokePluginsCommand.java:228) at com.alpha.pineapple.command.execution.CommandRunnerImpl.run(CommandRunnerImpl.java:88) at com.alpha.pineapple.execution.OperationTaskImpl.invokePlugins(OperationTaskImpl.java:391) at com.alpha.pineapple.execution.OperationTaskImpl.executeWithRegisteredContext(OperationTaskImpl.java:215) at com.alpha.pineapple.execution.OperationTaskImpl.execute(OperationTaskImpl.java:133) at com.alpha.pineapple.execution.AsyncOperationTaskImpl.execute(AsyncOperationTaskImpl.java:56) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.aop.interceptor.AsyncExecutionInterceptor$1.call(AsyncExecutionInterceptor.java:110) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at com.alpha.pineapple.plugin.docker.model.MapperImpl.mapContainerProperties(MapperImpl.java:403) at com.alpha.pineapple.plugin.docker.model.MapperImpl.mapContainerForCreation(MapperImpl.java:144) at com.alpha.pineapple.plugin.docker.operation.DeployConfiguration.createContainer(DeployConfiguration.java:277) at com.alpha.pineapple.plugin.docker.operation.DeployConfiguration.processModel(DeployConfiguration.java:178) at com.alpha.pineapple.plugin.docker.operation.DeployConfiguration.execute(DeployConfiguration.java:127) … 22 more

Updated 04/06/2017 10:26

Disallow failure of the coverage build in Travis?

python/core-workflow

Since python/cpython#1775 was merged, the coverage build in Travis actually passes all tests. Should we remove the allow_failures key to make sure that it continues to do so? That would mean an extra ~15 minutes between commit and approval from Travis, but as it’s already ~20 minutes, I don’t think it’s that big of a deal. In my experience, I’m not going to sit around waiting for 20 minutes anyway; I’ll have moved on to something else long before then and probably won’t check back until long after the build has finished.

Updated 28/05/2017 19:49 2 Comments

Run luacheck for all lua files in src

neovim/neovim

Lua files in src are growing more and more complex, so it should be a good idea to lint them as test files. In #6789 I have added linting for src/nvim/lua/vim.lua, but there is a bunch of other files in src, primary lists and generators, latter are rather complex and have started to contain modules. Enabling RunLuacheck.cmake for them should be a good idea.

Marking this as entry-level because despite of big number of errors all should be easy to fix: after all, luacheck is not a static analyzer.

Updated 19/06/2017 01:35 11 Comments

TST/CLN: Warnings from pytest 3.1+

pandas-dev/pandas

New versions of pytest print a useful summary of warnings that aren’t caught during the test run. Here’s a log from a couple days ago

<details>


=============================== warnings summary ===============================
pandas/tests/test_downstream.py::test_dask
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/dask/dataframe/__init__.py:3: DeprecationWarning: pandas.util.decorators is deprecated and will be removed in a future version, import from pandas.util
    from .core import (DataFrame, Series, Index, _Frame, map_partitions,

pandas/tests/test_downstream.py::test_xarray
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/xarray/core/formatting.py:16: FutureWarning: The pandas.tslib module is deprecated and will be removed in a future version.
    from pandas.tslib import OutOfBoundsDatetime

pandas/tests/test_downstream.py::test_statsmodels
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/statsmodels/statsmodels/compat/pandas.py:62: FutureWarning: The pandas.core.datetools module is deprecated and will be removed in a future version. Please use the pandas.tseries module instead.
    from pandas.core import datetools
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/patsy/util.py:652: DeprecationWarning: pandas.core.common.is_categorical_dtype is deprecated. import from the public API: pandas.api.types.is_categorical_dtype instead
    return safe_is_pandas_categorical_dtype(data.dtype)

pandas/tests/test_downstream.py::test_scikit_learn
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)

pandas/tests/test_downstream.py::test_seaborn
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/ipywidgets/widgets/widget_link.py:19: DeprecationWarning: Traits should be given as instances, not types (for example, `Int()`, not `Int`) Passing types is deprecated in traitlets 4.1.
    super(WidgetTraitTuple, self).__init__(Instance(Widget), Unicode, **kwargs)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/seaborn/seaborn/categorical.py:342: DeprecationWarning: pandas.core.common.is_categorical_dtype is deprecated. import from the public API: pandas.api.types.is_categorical_dtype instead
    elif is_categorical(y):

pandas/tests/test_downstream.py::test_pandas_datareader
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas_datareader/data.py:36: ResourceWarning: unclosed <socket.socket fd=17, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.7.36', 50017), raddr=('216.58.216.100', 80)>
    return GoogleDailyReader(*args, **kwargs).read()

pandas/tests/test_downstream.py::test_geopandas
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/fiona/drvsupport.py:143: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
    ogrdrv_names = gdalenv.start().drivers().keys()
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/fiona/collection.py:145: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
    self.env.__enter__()

pandas/tests/test_expressions.py::TestExpressions::()::test_integer_panel
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/panel.py:714: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, func)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/ops.py:1389: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, na_op)

pandas/tests/test_expressions.py::TestExpressions::()::test_float_panel
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/panel.py:714: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, func)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/ops.py:1389: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, na_op)

pandas/tests/test_expressions.py::TestExpressions::()::test_mixed_panel
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/panel.py:714: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, func)
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/ops.py:1389: DeprecationWarning: 
  Panel is deprecated and will be removed in a future version.
  The recommended way to represent these types of 3-dimensional data are with a MultiIndex on a DataFrame, via the Panel.to_frame() method
  Alternatively, you can use the xarray package http://xarray.pydata.org/en/stable/.
  Pandas provides a `.to_xarray()` method to help automate this conversion.

    return self._combine_const(other, na_op)

pandas/tests/dtypes/test_missing.py::test_array_equivalent_compat
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/numpy/core/numeric.py:2629: FutureWarning: elementwise == comparison failed and returning scalar instead; this will raise an error or perform elementwise comparison in the future.
    return bool(asarray(a1 == a2).all())

pandas/tests/frame/test_analytics.py::TestDataFrameAnalytics::()::test_corr_int_and_boolean
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/scipy/stats/stats.py:3577: RuntimeWarning: invalid value encountered in double_scalars
    size * (size - 1) * (size - 2))

pandas/tests/frame/test_analytics.py::TestDataFrameAnalytics::()::test_clip_mixed_numeric
  source:1893: DeprecationWarning: invalid escape sequence \d
  source:2464: DeprecationWarning: invalid escape sequence \(

pandas/tests/frame/test_operators.py::TestDataFrameOperators::()::test_boolean_comparison
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/internals.py:1153: DeprecationWarning: elementwise == comparison failed; this will raise an error in the future.
    result = func(values, other)

pandas/tests/indexing/test_coercion.py::TestFillnaSeriesCoercion::()::test_fillna_series_float64
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/internals.py:4785: ComplexWarning: Casting complex values to real discards the imaginary part
    nn_at = nn.astype(v.dtype)

pandas/tests/io/test_common.py::TestCommonIOCapabilities::()::test_read_fspath_all[reader7-os-/Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/tests/io/sas/data/test1.sas7bdat]
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/importlib/_bootstrap.py:205: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
    return f(*args, **kwds)

pandas/tests/io/parser/test_network.py::TestS3::()::test_s3_fails
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/tests/io/parser/test_network.py:173: ResourceWarning: unclosed <ssl.SSLSocket fd=28, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.7.36', 50425), raddr=('54.231.33.187', 443)>
    read_csv('s3://nyqpug/asdf.csv')
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/tests/io/parser/test_network.py:173: ResourceWarning: unclosed <ssl.SSLSocket fd=27, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.7.36', 50424), raddr=('54.231.40.83', 443)>
    read_csv('s3://nyqpug/asdf.csv')

pandas/tests/plotting/test_frame.py::TestDataFramePlots::()::test_line_colors
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/plotting/_core.py:179: UserWarning: 'colors' is being deprecated. Please use 'color'instead of 'colors'
    warnings.warn(("'colors' is being deprecated. Please use 'color'"

pandas/tests/plotting/test_hist_method.py::TestDataFramePlots::()::test_tight_layout
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/tests/plotting/test_hist_method.py:249: UserWarning: To output multiple subplots, the figure containing the passed axes is being cleared
    _check_plot_works(df.hist)

pandas/tests/plotting/test_misc.py::TestDataFramePlots::()::test_parallel_coordinates_with_sorted_labels
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/matplotlib/axes/_base.py:2917: UserWarning: Attempting to set identical left==right results
  in singular transformations; automatically expanding.
  left=0, right=0
    'left=%s, right=%s') % (left, right))

pandas/tests/plotting/test_series.py::TestSeriesPlots::()::test_pie_series
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/tests/plotting/test_series.py:296: DeprecationWarning: generator 'TestSeriesPlots.test_pie_series.<locals>.<genexpr>' raised StopIteration
    expected_texts = list(next(it) for it in itertools.cycle(iters))

pandas/tests/util/test_testing.py::TestAssertAlmostEqual::()::test_assert_almost_equal_edge_case_ndarrays
  /Users/taugspurger/Envs/pandas-dev/lib/python3.6/site-packages/pandas/pandas/core/dtypes/missing.py:308: DeprecationWarning: elementwise == comparison failed; this will raise an error in the future.
    return ((left == right) | (isnull(left) & isnull(right))).all()

-- Docs: http://doc.pytest.org/en/latest/warnings.html

</details>

Some of these will require updates to the test suite to just use the new behavior. Others should be explicitly caught with tm.assert_produces_warning. (I believe the downstream package warnings are already fixed in master for dask and statsmodels)

Updated 24/05/2017 20:05 1 Comments

Reducing Verbosity Terraform in Travis when building image

kubenow/KubeNow

When building image on GCE, during the builder post-processor a script is executed which run Terraform. Problem is that Terraform logs' verbosity switch directly to TRACE, producing a very large number of output lines, forcing travis to turn-off interactive log in favour of the raw one.

Possible Cause: Terraform is being run from Packer and not directly in Travis as part of the script: section

To do: Investigating what to do when Terraform is executed within Packer. Likely need to open an issue on terraform github repo

Updated 17/07/2017 13:47 1 Comments

Fork me on GitHub