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

start building helm nightly to cover gaps in helm release cycle

samsung-cnct/k2

helm does not cut official releases at the same time as kubernetes. we rely heavily on helm for providing ancillary services on kubernetes (monitoring, logging, CI that targets kubernetes, etc). as such we should be doing our best to be: - testing against alpha and beta versions of kubernetes - papering over the release lag between kubernetes and helm

this is a result of a discussion raised in #222

Updated 22/03/2017 23:14

Setup performance tests and metrics

rmariano/compr

Automatically run performance checks on the platform, that should be used to measure differences on changes, regression, etc. It is recommended to run as part of the CI along with the unit tests. It should be possible to compare performance across different branches and revisions.

Instrument the code, to support performance testability.

Have a separate target in Makefile.

Relevant metrics (to be reviewed):

  • Running time (latency) for one file
  • Running time for N file (traceability to determine how does it scale as more files are added).
  • CPU load (%, load average, etc.)
  • Memory usage.
  • I/O
Updated 22/03/2017 09:56

make check fails on ppc64el

laarid/package_debian-mesa

https://travis-ci.org/laarid/package_debian-mesa/jobs/213638438

  • lp_test_arit ``` $ cat build/src/gallium/drivers/llvmpipe/test-suite.log

Mesa 13.0.5: src/gallium/drivers/llvmpipe/test-suite.log

TOTAL: 5

PASS: 4

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: lp_test_arit

sin.v1(-3.92699075): ref = -0.707106709, out = 0.707106709, precision = -1.000000 bits, FAIL sin.v1(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v1(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v1(-2.3561945): ref = 0.707106769, out = -0.707106769, precision = -1.000000 bits, FAIL sin.v1(-1.57079637): ref = 1, out = -1, precision = -1.000000 bits, FAIL sin.v1(-0.785398185): ref = 0.707106769, out = -0.707106829, precision = -1.000000 bits, FAIL sin.v2(-3.92699075): ref = -0.707106709, out = 0.707106709, precision = -1.000000 bits, FAIL sin.v2(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v2(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v2(-2.3561945): ref = 0.707106769, out = -0.707106769, precision = -1.000000 bits, FAIL sin.v2(-1.57079637): ref = 1, out = -1, precision = -1.000000 bits, FAIL sin.v2(-0.785398185): ref = 0.707106769, out = -0.707106829, precision = -1.000000 bits, FAIL sin.v4(-3.92699075): ref = -0.707106709, out = 0.707106709, precision = -1.000000 bits, FAIL sin.v4(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v4(-3.14159274): ref = -8.74227766e-08, out = 8.74227766e-08, precision = -1.000000 bits, FAIL sin.v4(-2.3561945): ref = 0.707106769, out = -0.707106769, precision = -1.000000 bits, FAIL sin.v4(-1.57079637): ref = 1, out = -1, precision = -1.000000 bits, FAIL sin.v4(-0.785398185): ref = 0.707106769, out = -0.707106829, precision = -1.000000 bits, FAIL round.v1(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL round.v1(0.5): ref = 0, out = 1, precision = -inf bits, FAIL FAIL lp_test_arit (exit status: 1) ```

Updated 22/03/2017 08:57

make check fails on mips64el

laarid/package_debian-mesa

https://travis-ci.org/laarid/package_debian-mesa/jobs/213638436

  • gbm-symbols-check ``` $ cat build/src/gbm/test-suite.log

Mesa 13.0.5: src/gbm/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: gbm-symbols-check

_ftext FAIL gbm-symbols-check (exit status: 1) ```

  • wayland-egl-symbols-check ``` $ cat build/src/egl/wayland/wayland-egl/test-suite.log

Mesa 13.0.5: src/egl/wayland/wayland-egl/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: wayland-egl-symbols-check

_ftext FAIL wayland-egl-symbols-check (exit status: 1) ```

  • egl-symbols-check ``` $ cat build/src/egl/test-suite.log

Mesa 13.0.5: src/egl/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: egl-symbols-check

_ftext FAIL egl-symbols-check (exit status: 1) ```

Updated 22/03/2017 08:43

make check fails on armhf: glsl/tests/cache-test and src/gallium/drivers/llvmpipe/lp_test_arit

laarid/package_debian-mesa

https://travis-ci.org/laarid/package_debian-mesa/jobs/213638433

  • lp_test_arit ``` $ cat build/src/gallium/drivers/llvmpipe/test-suite.log

Mesa 13.0.5: src/gallium/drivers/llvmpipe/test-suite.log

TOTAL: 5

PASS: 4

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: lp_test_arit

round.v1(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL round.v1(0.5): ref = 0, out = 1, precision = -inf bits, FAIL round.v4(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL round.v4(0.5): ref = 0, out = 1, precision = -inf bits, FAIL floor.v2(-1.40129846e-45): ref = -1, out = 0, precision = -0.000000 bits, FAIL floor.v4(-1.40129846e-45): ref = -1, out = 0, precision = -0.000000 bits, FAIL ceil.v2(1.40129846e-45): ref = 1, out = 0, precision = -0.000000 bits, FAIL ceil.v4(1.40129846e-45): ref = 1, out = 0, precision = -0.000000 bits, FAIL fract.v2(1.40129846e-45): ref = 1.40129846e-45, out = 0, precision = -0.000000 bits, FAIL fract.v2(-1.40129846e-45): ref = 0.99999994, out = -0, precision = -0.000000 bits, FAIL fract.v2(5.8799997e-39): ref = 5.8799997e-39, out = 0, precision = -0.000000 bits, FAIL fract.v4(1.40129846e-45): ref = 1.40129846e-45, out = 0, precision = -0.000000 bits, FAIL fract.v4(-1.40129846e-45): ref = 0.99999994, out = -0, precision = -0.000000 bits, FAIL fract.v4(5.8799997e-39): ref = 5.8799997e-39, out = 0, precision = -0.000000 bits, FAIL FAIL lp_test_arit (exit status: 1) ```

  • glsl/tests/cache-test ``` $ cat build/src/compiler/test-suite.log

Mesa 13.0.5: src/compiler/test-suite.log

TOTAL: 10

PASS: 9

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: glsl/tests/cache-test

Mesa warning: Failed to create ./cache-test-tmp/xdg-cache-home for shader cache (No such file or directory)—disabling.

Mesa warning: Failed to create ./cache-test-tmp/mesa-glsl-cache-dir for shader cache (No such file or directory)—disabling.

Error: Test ‘no eviction before overflow with MAX_SIZE=1M’ failed: Expected=3, Actual=0 Error: Test ‘eviction after overflow with MAX_SIZE=1M’ failed: Expected=2, Actual=0 FAIL glsl/tests/cache-test (exit status: 1) ```

Updated 22/03/2017 08:44 1 Comments

make check fails on mips and mipsel

laarid/package_debian-mesa

mips: https://travis-ci.org/laarid/package_debian-mesa/jobs/213638435 mipsel: https://travis-ci.org/laarid/package_debian-mesa/jobs/213638437

  • undefined reference to __sync_val_compare_and_swap_8, __sync_add_and_fetch_8: u_atomic_test.o: In function `test_atomic_assign_int64_t': ./build/src/util/../../../src/util/u_atomic_test.c:137: undefined reference to `__sync_val_compare_and_swap_8' ... u_atomic_test.o: In function `test_atomic_8bits_int64_t': ./build/src/util/../../../src/util/u_atomic_test.c:137: undefined reference to `__sync_add_and_fetch_8' ... collect2: error: ld returned 1 exit status Makefile:920: recipe for target 'u_atomic_test' failed make[6]: *** [u_atomic_test] Error 1 make[6]: Leaving directory '/home/travis/build/laarid/package_debian-mesa/build/src/util'

  • gbm-symbols-check ``` $ cat build/src/gbm/test-suite.log


Mesa 13.0.5: src/gbm/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: gbm-symbols-check

_ftext FAIL gbm-symbols-check (exit status: 1) ```

  • wayland-egl-symbols-check ``` $ cat build/src/egl/wayland/wayland-egl/test-suite.log

Mesa 13.0.5: src/egl/wayland/wayland-egl/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: wayland-egl-symbols-check

_ftext FAIL wayland-egl-symbols-check (exit status: 1) ```

  • egl-symbols-check ``` $ cat build/src/egl/test-suite.log

Mesa 13.0.5: src/egl/test-suite.log

TOTAL: 1

PASS: 0

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: egl-symbols-check

_ftext FAIL egl-symbols-check (exit status: 1) ```

Updated 22/03/2017 08:46

make check fails on arm64: src/gallium/drivers/llvmpipe/lp_test_arit FAIL

laarid/package_debian-mesa

https://travis-ci.org/laarid/package_debian-mesa/jobs/213638431

  • lp_test_arit ``` $ cat build/src/gallium/drivers/llvmpipe/test-suite.log

Mesa 13.0.5: src/gallium/drivers/llvmpipe/test-suite.log

TOTAL: 5

PASS: 4

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: lp_test_arit

round.v1(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL round.v1(0.5): ref = 0, out = 1, precision = -inf bits, FAIL round.v4(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL round.v4(0.5): ref = 0, out = 1, precision = -inf bits, FAIL FAIL lp_test_arit (exit status: 1) ```

Updated 22/03/2017 08:46

Support VSIX Templates

Kentico/cloud-boilerplate-net

Inspiration: https://github.com/ASP-NET-MVC-Boilerplate/Templates#dotnet-new

Other resources regarding the new templating engine:

Wiki: https://github.com/dotnet/templating/wiki/%22Runnable-Project%22-Templates Existing templates: https://github.com/dotnet/templating/wiki/Available-templates-for-dotnet-new http://dotnetthoughts.net/create-a-dot-net-new-project-template-in-dot-net-core/

Updated 21/03/2017 13:24

HttpConnectorTest intermittent CI failure

ScriptFUSION/Porter

Travis occasionally fails to pass HttpConnectorTest with an error similar to the following.

There was 1 error:

1) ScriptFUSIONTest\Functional\Porter\Net\Http\HttpConnectorTest::testConnectionToLocalWebserver
ScriptFUSION\Retry\FailingTooHardException: Operation failed after 5 attempt(s).

/home/travis/build/ScriptFUSION/Porter/vendor/scriptfusion/retry/src/retry.php:29
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:96
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:34

Caused by
ScriptFUSION\Porter\Net\Http\HttpConnectionException: file_get_contents(http://[::1]:12345/test?baz=qux): failed to open stream: Connection refused

/home/travis/build/ScriptFUSION/Porter/src/Net/Http/HttpConnector.php:65
/home/travis/build/ScriptFUSION/Porter/src/Connector/CachingConnector.php:62
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:110
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:86
/home/travis/build/ScriptFUSION/Porter/vendor/scriptfusion/retry/src/retry.php:26
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:96
/home/travis/build/ScriptFUSION/Porter/test/Functional/Porter/Net/Http/HttpConnectorTest.php:34

This never used to be a problem, and thanks to the five retries it should have plenty of time to spin up the server. However, this is also the first test in the suite so it may have something to do with PHPUnit start-up time. We should consider moving slower tests to the end of the suite, and if that doesn’t work, we’ll have to increase the retry delay coefficient.

Updated 16/03/2017 16:42

circle ci でたまに apt-get に失敗する

srz-zumix/iutest

https://circleci.com/gh/srz-zumix/iutest/622#tests/containers/1

sudo apt-get -qq install clang-3.9
E: Unable to locate package clang-3.9
E: Couldn't find any package by regex 'clang-3.9'

sudo apt-get -qq install clang-3.9 returned exit code 100

Action failed: sudo apt-get -qq install clang-3.9

その前の update で失敗しているので、リトライかなにかで回避したい。 ``` Err http://apt.llvm.org llvm-toolchain-trusty-3.9 InRelease

Err http://apt.llvm.org llvm-toolchain-trusty-3.9 Release.gpg Unable to connect to apt.llvm.org:http: ```

Updated 17/03/2017 00:57

Cypress fails to run in a docker container within CircleCI

cypress-io/cypress

If you create a docker container with Cypress installed (you can use this semi-official container if you want: https://hub.docker.com/r/bahmutov/cypress-image/) and try to use it in CircleCI, cypress will not work. - Most commands just hang with no output, even if you set CYPRESS_DEBUG=true. - It seems that this could be related to network connectivity because if you run the container without –net=host then cypress will not hang (it will just not work because it will not be able to connect to your server). - Does not seem to be a dependency issue because that same container runs fine in a local ubuntu machine. - Tested both in CircleCI Ubuntu 12.04 and 14.04 images

Updated 18/03/2017 20:19 1 Comments

create CI job that verifies non-supported kubernetes templates are removed

samsung-cnct/k2

as of https://github.com/samsung-cnct/k2/issues/222#issuecomment-284583580 we will be introducing template directories and ansible checks that should be removed when we no longer support that version.

create a CI job that checks the source code for no longer supported templates and version checks. at this moment I am unsure how we are tracking what the supported versions of kubernetes are so that may also be something that needs to be determined here.

Updated 20/03/2017 17:30 2 Comments

Crypto.AEAD.Encoding works on my OSX machine but not on CI

FStarLang/FStar
jonathan@chartreuse:~/Code/fstar/examples/low-level/crypto (master) $ make Crypto.AEAD.Encoding.fst-ver OTHERFLAGS=--record_hints\ --z3rlimit\ 1024
../../../bin/fstar.exe --fstar_home ../../.. --max_fuel 4 --initial_fuel 0 --max_ifuel 2 --initial_ifuel 0 --z3rlimit 20  --use_hints --record_hints --z3rlimit 1024 \
    --include ../../../ulib/hyperstack --include hacl \
    --__temp_no_proj Crypto.Symmetric.MAC \
    --verify_module Crypto.AEAD.Encoding \
    Crypto.AEAD.Encoding.fst
Verified module: Crypto.AEAD.Encoding (361952 milliseconds)
All verification conditions discharged successfully

but:

./Crypto.AEAD.Encoding.fst(405,0-460,5): (Error) Unknown assertion failed

(on a7204466)

this is WITH hints regenerated.

Multiplying the z3rlimit by 10 gives:

All verification conditions discharged successfully
.\Crypto.AEAD.Encoding.fst(454,6-454,12): (Error) assertion failed (see .\Crypto.AEAD.Encoding.fst(454,12-454,46))
Verified module: Crypto.AEAD.Encoding (388249 milliseconds)

(on d9089ac0)

Setting it to --lax to the moment but any help would be appreciated.

Thanks,

Jonathan

CC @nikswamy @s-zanella @wintersteiger

Updated 22/03/2017 12:53 7 Comments

ci: remove travis

nodejs/citgm

we no longer need travis as we are now using Jenkins CI build statuses inline in PRs #358. We will also need to remove citgm from the travis configuration

<!– Thank you for your pull request. Please provide a description above and review the requirements below. –>

Checklist

<!– Remove items that do not apply. For completed items, change [ ] to [x]. –>

  • [x] npm test passes
  • [x] contribution guidelines followed here
  • [x] commit message follows commit guidelines
Updated 01/03/2017 08:26 2 Comments

Enable inline Jenkins build status on PRs

nodejs/citgm

Opening this issue continuing a discussion ignited over in https://github.com/nodejs/github-bot/issues/82.

Before I start fiddling around with getting Jenkins to report build statuses to the github-bot, I want to confirm which build we should do this on? I’m assuming citgm-continuous-integration or citgm-smoker?

Would you agree that we can start off by setting up Jenkins to report build status to a PR specified when starting a build, like we do in nodejs/node, or do you have something else in mind?

/cc @gibfahn @gdams

Updated 09/03/2017 21:49 8 Comments

why travis job decides to build dependency?

mapnik/mapnik

https://travis-ci.org/mapnik/mapnik/jobs/204170476#L365

Mason decided to build gdal, which took 15mins out of the 19 the whole job ran. Why? It’s not good, especially for OSX jobs that already lag behind.

Not to mention something’s broken at the end of the gdal build, it prints the gdal-config script to console and then apparently invokes it without parameters, from the usage messages it appears even "$0" is empty.

Updated 22/02/2017 14:22

Set up sass-lint

KeitIG/museeks
  • Add .sass-lint.yml
  • Add sass-lint to CI
# sass-lint config generated by make-sass-lint-config v0.2.2
#
# The following scss-lint Linters are not yet supported by sass-lint:
# ChainedClasses, DisableLinterReason, ElsePlacement, PrivateNamingConvention
# PropertyCount, PseudoElement, SelectorDepth, SpaceAfterComment
# SpaceAfterVariableColon, SpaceAroundOperator, TrailingWhitespace, UnnecessaryParentReference
# Compass::*
#
# The following settings/values are unsupported by sass-lint:
# Linter Comment, option "style"
# Linter Indentation, option "allow_non_nested_indentation"
# Linter Indentation, option "character"
# Linter NestingDepth, option "ignore_parent_selectors"
# Linter PropertySortOrder, option "min_properties"
# Linter PropertySortOrder, option "separate_groups"
# Linter PropertySpelling, option "disabled_properties"
# Linter SpaceBeforeBrace, option "allow_single_line_padding"
# Linter VendorPrefix, option "identifier_list"

files:
  include: 'client/stylesheets/**/*.s+(a|c)ss'
options:
  formatter: stylish
  merge-default-rules: false
rules:
  bem-depth:
    - 0
    - max-depth: 2
  border-zero:
    - 2
    - convention: zero
  brace-style:
    - 2
    - allow-single-line: false
  class-name-format:
    - 2
    - convention: hyphenatedlowercase
  clean-import-paths:
    - 2
    - filename-extension: false
      leading-underscore: false
  empty-line-between-blocks:
    - 2
    - ignore-single-line-rulesets: true
  extends-before-declarations: 2
  extends-before-mixins: 2
  final-newline:
    - 2
    - include: true
  force-attribute-nesting: 2
  force-element-nesting: 2
  force-pseudo-nesting: 2
  function-name-format:
    - 2
    - allow-leading-underscore: true
      convention: hyphenatedlowercase
  hex-length:
    - 2
    - style: long
  hex-notation:
    - 2
    - style: uppercase
  id-name-format:
    - 2
    - convention: hyphenatedlowercase
  indentation:
    - 2
    - size: 4
  leading-zero:
    - 2
    - include: false
  mixin-name-format:
    - 2
    - allow-leading-underscore: true
      convention: hyphenatedlowercase
  mixins-before-declarations: 2
  nesting-depth:
    - 1
    - max-depth: 3
  no-color-keywords: 2
  no-color-literals: 2
  no-css-comments: 1
  no-debug: 2
  no-duplicate-properties: 2
  no-empty-rulesets: 2
  no-extends: 0
  no-ids: 2
  no-important: 1
  no-invalid-hex: 2
  no-mergeable-selectors: 2
  no-misspelled-properties:
    - 2
    - extra-properties: []
  no-qualifying-elements:
    - 2
    - allow-element-with-attribute: false
      allow-element-with-class: false
      allow-element-with-id: false
  no-trailing-zero: 2
  no-transition-all: 1
  no-url-protocols: 1
  no-vendor-prefixes:
    - 1
    - additional-identifiers: []
      excluded-identifiers: []
  placeholder-in-extend: 2
  placeholder-name-format:
    - 2
    - convention: hyphenatedlowercase
  property-sort-order:
    - 2
    - ignore-custom-properties: false
  property-units:
    - 2
    - global:
        - ch
        - em
        - ex
        - rem
        - cm
        - in
        - mm
        - pc
        - pt
        - px
        - q
        - vh
        - vw
        - vmin
        - vmax
        - deg
        - grad
        - rad
        - turn
        - ms
        - s
        - Hz
        - kHz
        - dpi
        - dpcm
        - dppx
        - '%'
      per-property: {}
  quotes:
    - 2
    - style: single
  shorthand-values:
    - 2
    - allowed-shorthands:
        - 2
        - 2
        - 3
        - 4
  single-line-per-selector: 2
  space-after-bang:
    - 2
    - include: false
  space-after-colon:
    - 2
    - include: true
  space-after-comma:
    - 2
    - include: true
  space-before-bang:
    - 2
    - include: true
  space-before-brace:
    - 2
    - include: true
  space-before-colon: 2
  space-between-parens:
    - 2
    - include: false
  trailing-semicolon: 2
  url-quotes: 2
  variable-for-property:
    - 0
    - properties: []
  variable-name-format:
    - 2
    - allow-leading-underscore: true
      convention: hyphenatedlowercase
  zero-unit: 2
Updated 20/02/2017 09:52

Run examples as part of CI builds

RossBencina/StaticMode

Right now, the CI builds compile the examples (and will fail the CI process if there are any issues). But they don’t run the examples. Ideally we would:

  • Run each example (this is easy to set up by adding the example as a test in CMakeLists.txt using add_test (see CMakeLists.txt in the tests/ directory for an example).
  • Verify that the output is as expected (not sure how to do this, can CMake do it?) maybe a python script?)
Updated 20/02/2017 09:35

Travis-CI: Use docker images for linux builds

LibrePCB/LibrePCB

On Travis it’s possible to use docker images to build and run the tests, see Using Docker in Builds.

Maybe that would be a great solution for LibrePCB as it gives us some advantages: - Faster CI feedback because the installation of all dependencies (e.g. apt-get install) is no longer required (these dependencies come pre-installed in the image). Needs to be confirmed because I don’t know how long Travis requires to pull the image from docker hub. - Instead of only installing binaries, it would be even possible to build some tools from source without affecting the CI feedback time. For example linuxdeployqt may be a candidate for building from source. - It’s easier (resp. even possible) to build and run LibrePCB on other distributions than the (very few) ones which are available on Travis. This is extremely helpful for development, testing and deployment! - Our already existing Dockerfile would make more sense: - It would no longer contain redundant information which is already in the .travis-ci.yml file. - We would be forced to actively maintain the Dockerfile. At the moment we have no strong motivation to maintain it and thus it’s easy to forget adding new dependencies and so on. - We would need to upload our image to Docker Hub. This would make using the image much simpler as cloning the LibrePCB repository is no longer required to get the image.

Of course there may appear some technical problems which need to be solved until all of this works properly :wink:

Updated 06/03/2017 07:29 2 Comments

create jenkins-ci project plan

samsung-cnct/k2

our current jenkins CI system (kraken-ci) is unmaintained, based on jenkins v1 and the instructions to rebuild no longer work. we are going to abandon this project in favor of using a kubernetes-based jenkins build system built on jenkins v2.

this ticket will cover the basic planning and initial tickets for the new ci system

Updated 27/03/2017 05:29 12 Comments

Run coverage.py with coverage/fullcoverage/encodings.py

python/core-workflow

https://github.com/nedbat/coveragepy/blob/master/coverage/fullcoverage/encodings.py is a hack which makes sure that coverage.py is imported early enough to cover modules that are imported during interpreter startup. Previously it wasn’t included with coverage.py, but @nedbat was nice enough to add fullcoverage to coverage.py in https://github.com/nedbat/coveragepy/commit/3962bc4387e4ca69d1e2df280b1021b3db9326fd for its next release. So this issue is to make sure that no one forgets to take advantage of fullcoverage once it’s available on PyPI.

Updated 03/03/2017 06:55 1 Comments

pytest followup

pandas-dev/pandas

Followup issues to https://github.com/pandas-dev/pandas/pull/13856 - [x] remove nose entirely (#15368) - [x] fix yield base tests, see here. in computation and test_pickle.py, replace with paramterization / fixtures. (#15406) - [x] yield based tests in: - [x] frame/test_query_eval.py - [x] io/test_packers.py (#15427) - [x] io/test_pickle.py (#15416) - [x] test_internals.py (#15708) - [x] test_window.py (#15708) - [x] use pytest-dist (#15369) - [x] change generator based tests to addopts = --disable-pytest-warnings from setup.cfg (#15708) - [ ] figure out getlocale failure on travis in pandas/tools/tests/test_util.py:TestLocaleUtils.test_set_locale - [ ] replace @network using pytest.mark (add other markers?) - [ ] fix doc/source/contributing.rst reference to pd.test - [x] move conftest.py to top-level (#15731) - [ ] use parametrize - [ ] use fixtures - [x] list of skipped tests is failing (#15408) - [x] nose.SkipTest -> pytest.skip() (or @pytest.mark.skip or skipif) (#15368)

Updated 23/03/2017 13:59 3 Comments

Tool bootstrap version check for git incorrectly fails on ubuntu and cygwin

mysensors/MySensors

from @tbowmo: ```

.mystools/bootstrap-dev.sh Checking operating system support: linux-gnu… Checking github ‘origin’ & ‘upstream’ remotes… Git “upstream” remote not found or incorrectly defined. Configuring remote upstream –> https://github.com/mysensors/MySensors.git… Checking tool/utility prerequisites… Found git however, version 2.0 or greater is required… Install git 2.0 or greater and re-run .mystools/bootstrap-dev.sh thomas at thomas-ThinkPad-L450 in ~/tmp/MySensors git:(development) ✗ git –version git version 2.9.3 thomas at thomas-ThinkPad-L450 in ~/tmp/MySensors git:(development) ✗ ```

from @mfalkvidd:

``` Checking tool/utility prerequisites… Found git however, version 2.0 or greater is required… Install git 2.0 or greater and re-run .mystools/bootstrap-dev.sh Mikael @ yoga ~/workspace/MySensors heads/mfalkvidd/master $ git –version git version 2.8.3

  • check_tool_prerequisite git 2.0
  • is_installed git
  • which git ++ git –version ++ sed -ne ’s/[^0-9](([0-9].){0,4}[0-9][^.])./\1/p'
  • local version= ++ ver +++ echo ‘’ +++ tr . ‘ ’ ++ printf %03d%03d%03d%03d ++ ver 2.0 +++ echo 2.0 +++ tr . ‘ ’ ++ printf %03d%03d%03d%03d 2 0
  • ‘[’ 000000000000 -lt 002000000000 ‘]’
  • warn ‘Found git however, version 2.0 or greater is required…’
  • IFS=‘ ’
  • printf ‘\e[93m%s\e[m\n’ ‘Found git however, version 2.0 or greater is required…’```

Most likely a regex portability issue.

cc: @fallberg

Updated 07/02/2017 16:59

Hail CI does not compile using Clang

hail-is/hail

This opens the possibility for compiler differences to fail builds for our users.

The CI server should simply set CXX and CC to clang and rebuild hail. Moreover, we need to ensure the hail build system passes these variables all the way down to libsimdpp.

Updated 15/02/2017 17:07 7 Comments

GitHub Pages fails to publish doxygen output because of too large repository

LibrePCB/LibrePCB

Travis builds the doxygen documentation for each branch and pushes it to the LibrePCB-Doxygen repository. For details have a look at the implementation in dev/travis/update_doxygen.sh. The HTML output is then published using GitHub Pages.

But the problem is that the doxygen documentation of deleted branches stays there forever, and thus the LibrePCB-Doxygen repository grows more and more. And after reaching a specific size, GitHub Pages refuses to update the published page. This did already happen a few times. Because of this, I changed the implementation to always append changes to the last commit (so there are always only two commits in the LibrePCB-Doxygen repository). Now the repository size grows slower, but it still grows.

I think it should be enough to change the implementation to let it remove the generated documentation of removed branches. But maybe there would be a completely different approach which works better? In fact, we don’t even need a Git repository for hosting the doxygen output, this was just the easiest solution for publishing the documentation ;)

Updated 17/03/2017 22:47

[RFC] CI testing of MSSQL on windows with AppVeyor

doctrine/dbal

AppVeyor CI testing should be added to this repository. AppVeyor is another continuous integration platform which is free for open source projects and offers CI testing support for GitHub repositories. The big difference is AppVeyor platform specializes in testing on the Windows environment. This would enable the test suite to be ran on a Windows environment and include test coverage for the Microsoft SQL Server database driver.

Updated 26/01/2017 21:00 2 Comments

Fix CI tests

EA31337/EA31337-classes

Two CI tests to fix: Appveyor & Travis

Files to fix: *.mqh

Language: MQL (you need to install Metaeditor to compile the files). After installation, copy/clone the repo under MQL5 or MQL5/Include folder of the platform, so you can open them and compile. Other dependent repos should be cloned recursively into MQL5/Include (e.g. strategies).

The redefinition/already-defined errors happens, because include-files are including another .mqh files (<> instead of "") and compiler probably doesn’t recognise that these are the same files. After that there should be only very few errors.

Updated 25/01/2017 03:13

How to organise the Driver interface?

paulgibbs/behat-wordpress-extension

As noted via e-mail, the Driver acts as an interface for communication between Behat and WordPress (creating, deleting, asserting properties of) content/users/options/terms etc.

The Driver, therefore, could grow quite large. One suggestion is to compartmentalize each WordPress ‘entity’ (content, users, etc) So rather than:

$driver->createTerm()
$driver->createContent()

it would be

$driver->term->create()
$driver->content->create()

I don’t foresee any reason to be able to swap out, say, the $driver-term instance, but this would at least allow us to group methods which are logically consistent, and keep classes smaller.

Updated 02/03/2017 10:42 3 Comments

Travis CI, random issues running qucs-test.

Qucs/qucs

After the OSX image was downgraded to xcode6.4 random issues started to show up when running qucs-test.

Examples of errors below: ```

Project : /Users/travis/build/Qucs/qucs/qucs-test/testsuite/DC_AC_bbv_prj Running : /Users/travis/build/Qucs/qucs/qucs-core/src/qucsator -i /Users/travis/build/Qucs/qucs/qucs-test/testsuite/DC_AC_bbv_prj/netlist.txt -o /Users/travis/build/Qucs/qucs/qucs-test/testsuite/DC_AC_bbv_prj/test_bbv.dat WARNING:Process return code: -11 Failed with error code, saving: /Users/travis/build/Qucs/qucs/qucs-test/testsuite/DC_AC_bbv_prj/error_code.txt ```

Terminating process, timed out 1 s
 +++ Qucsator ERROR +++ 
 +++  no result +++ 
[  >FAIL ]  TEST 069  [ arccos ] ==> [TAG_DOUBLE] = ['TAG_DOUBLE']
---
.DC:DC1 Temp="26.85" reltol="0.001" abstol="1 pA" vntol="1 uV"saveOPs="no" MaxIter="150" saveAll="no" convHelper="none" Solver="CroutLU"
Eqn:Eqn1 check="arccos(-1.0)" Export="yes"
Expected:
arccos(-1.0)
    3.14159265359
Got:
Traceback (most recent call last):
  File "run_equations.py", line 667, in <module>
    with open(outDat, 'r') as myDat:
IOError: [Errno 2] No such file or directory: '/tmp/qucstest/test068.dat'
make: *** [eqncheck] Error 1
The command "if [ "$OSX" = true ]; then make; make qucscheck; make eqncheck; else make distcheck DISTCHECK_CONFIGURE_FLAGS="${DISTCHECK_CONFIGURE_FLAGS}"; fi" exited with 2.

I tried disabling qucsatorcheck, but now the issues moved up to eqncheck. It might be related to the multiprocessing or numpy (used to calculate the differences).

Updated 13/02/2017 21:47 3 Comments

Flakyness in CI

nodejs/citgm

<img width=“946” alt=“screen shot 2017-01-17 at 12 23 54 pm” src=“https://cloud.githubusercontent.com/assets/498775/22031815/dddcfec2-dcaf-11e6-939b-0069034d6daf.png”>

We should dig into why this is happening

https://travis-ci.org/nodejs/citgm/jobs/192648256

Updated 31/01/2017 15:30

use concourse pool-resource for environment locking - Story Id: 136513081

cf-tm-bot/routing

Instead of having to manually communicate to the rest of the team via slack to see whether an environment is in use or not, let’s try to use the concourse pool-resource. This type of resource is usually used to coordinate a pool of resources, but we would have one environment per pool (serving as a mutex lock).

If this looks like a lot of work, we can always postpone and discuss further as a team. Some scripts for manually claiming/unclaiming envs would probably be useful as well.


Mirrors: story 136513081 submitted on Dec 21, 2016 UTC - Requester: Aaron Hurley - Estimate: 0.0

Updated 12/01/2017 17:27

Change final release job in routing-acceptance pipeline to use git tags instead of semver - Story Id: 136976511

cf-tm-bot/routing

We want to switch to using git tags as the source of truth for release versioning instead of the semver concourse resource. We can look to how cf-release and routing-release versions are being created for reference on the switch


Mirrors: story 136976511 submitted on Jan 3, 2017 UTC - Requester: Swetha Repakula - Estimate: 0.0

Updated 12/01/2017 17:27

Proposal: run workflows from installed path inside Docker

poldracklab/fmriprep

To avoid that installation errors like #300 pass unnoticed, we could/should run the smoke tests from the general installation path inside docker.

That would require a regular installation (using python setup.py install) instead of a development installation, and implicitly help test that the package installation works well.

WDYT?

Updated 14/03/2017 19:02 4 Comments

plutonium-data-filter #1 failed

lordoftheflies/plutonium-data-filter

Build ‘plutonium-data-filter’ is failing!

Last 50 lines of build output:

Started by user Hegedűs László
Building in workspace /var/lib/jenkins/workspace/plutonium-data-filter
Cloning the remote Git repository
Cloning repository git@github.com:lordoftheflies/plutonium-data-filter.git
 > /usr/bin/git init /var/lib/jenkins/workspace/plutonium-data-filter # timeout=10
Fetching upstream changes from git@github.com:lordoftheflies/plutonium-data-filter.git
 > /usr/bin/git --version # timeout=10
using GIT_SSH to set credentials My Github user
 > /usr/bin/git fetch --tags --progress git@github.com:lordoftheflies/plutonium-data-filter.git +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git config remote.origin.url git@github.com:lordoftheflies/plutonium-data-filter.git # timeout=10
 > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git config remote.origin.url git@github.com:lordoftheflies/plutonium-data-filter.git # timeout=10
Cleaning workspace
 > /usr/bin/git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > /usr/bin/git clean -fdx # timeout=10
Fetching upstream changes from git@github.com:lordoftheflies/plutonium-data-filter.git
using GIT_SSH to set credentials My Github user
 > /usr/bin/git fetch --tags --progress git@github.com:lordoftheflies/plutonium-data-filter.git +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > /usr/bin/git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 92f60b62dc69f10a107759a5ef759f40e0134473 (refs/remotes/origin/master)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 92f60b62dc69f10a107759a5ef759f40e0134473
First time build. Skipping changelog.
ERROR: /var/lib/jenkins/workspace/plutonium-data-filter/.travis.yml (No such file or directory) (Java::JavaIo::FileNotFoundException)
java.io.FileInputStream.open0(Native Method)
java.io.FileInputStream.open(java/io/FileInputStream.java:195)
java.io.FileInputStream.<init>(java/io/FileInputStream.java:138)
hudson.FilePath.read(hudson/FilePath.java:1754)
java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
RUBY.read(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/filepath.rb:27)
RUBY.build(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/models/travis_yml_script.rb:14)
RUBY.perform(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/models/travis_yml_builder.rb:27)
RUBY.perform(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/tasks/build_step_proxy.rb:14)
RUBY.boolean_result(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/tasks/build_step_proxy.rb:22)
RUBY.perform(/var/lib/jenkins/plugins/travis-yml/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/tasks/build_step_proxy.rb:13)
hudson.tasks.BuildStepMonitor$1.perform(hudson/tasks/BuildStepMonitor.java:20)
hudson.model.AbstractBuild$AbstractBuildExecution.perform(hudson/model/AbstractBuild.java:779)
hudson.model.Build$BuildExecution.build(hudson/model/Build.java:205)
hudson.model.Build$BuildExecution.doRun(hudson/model/Build.java:162)
hudson.model.AbstractBuild$AbstractBuildExecution.run(hudson/model/AbstractBuild.java:534)
hudson.model.Run.execute(hudson/model/Run.java:1728)
hudson.model.FreeStyleBuild.run(hudson/model/FreeStyleBuild.java:43)
hudson.model.ResourceController.execute(hudson/model/ResourceController.java:98)
hudson.model.Executor.run(hudson/model/Executor.java:404)

Build step 'Build using .travis.yml' marked build as failure

Changes since last successful build:

View full output

Updated 02/01/2017 00:35 3 Comments

Gradle build issue

appium/java-client

Description

There is a problem with the gradle building/publishing. Take a look at this file. It requires hardcoded parameters. This information is sensitive. And it could be commited eventually.

Environment

Doesn’t matter. It needs for gradle v > 2.14

Details

Could we add something like this tasks.withType(signing) { //trying to extract credentials and other secret information from the gradle.properties //if there is no data // it tries to get it from System.properties }

That way we could configure CI.

Updated 25/02/2017 18:57 1 Comments

tests: All functional tests should change to use prebuilt vagrant boxes

heketi/heketi

Currently we use generic Vagrant boxes, which we then setup as we want using Ansible. This model is completely unpredictable as time goes by because many things change. Instead, we need to change our tests to use prebuilt vagrant boxes, which have been setup for our tests. This means that we also need a directory in Heketi so that anyone can build the boxes automatically, then the boxes can submit to Vagrant Atlas.

@heketi/dev

Updated 10/02/2017 19:56

Run integration tests when building from 3rd party forks

ProcedureKit/ProcedureKit

At the moment, when building ProcedureKit we trigger CI on TryProcedureKit to build an app which uses the same commit via CocoaPods. This is done by having ProcedureKit as a submodule, and then checking out the same commit.

However, when a contributor submits a PR, this commit only exists in their fork, not in the upstream repo. Therefore, in these situations, we need to add the 3rd party repo as a new remote in the submodule, and then checkout the commit.

Additionally, we’ll need to remove the remote afterwards.

Updated 08/02/2017 21:01

Travis CI build failures

offa/NBCndUnit

Travis CI build failures on master and netbeans_dev_builds branches. Jobs were executed by cron (#24).

$ mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk/bin/java
[…]
Your build has been stopped.

Only JDK7 Jobs are affected, JDK8 works correct.

Updated 23/02/2017 15:27 6 Comments

`cypress ci` does not issue proper exit code in Codeship CI

cypress-io/cypress

I am having an issue when running tests in Codeship. The tests should exit with the number of failures, but instead it times out.

Error Message

--------------------------------------------------------------------------------
This command didn't output anything for 10 minutes, thus we stopped it.
Please make sure your steps regularly print to standard out or standard error.
If the error is on our end please inform us so we can help you to fix this.
--------------------------------------------------------------------------------

Screenshot screen shot 2016-12-06 at 11 18 27 am

Codeship’s support team input

I took a look at some of your builds and I’m wondering more about the cypress ci command. It looks like it finishes, but maybe isn’t giving an exit code? Codeship relies on scripts/commands providing a meaningful exit code to know when the command is done and also to then know to move on to the next command or if the build should be failed.

Updated 06/02/2017 21:41 10 Comments

Develop commit-msg hook to catch "bad commit messages" before git commit

mysensors/MySensors

Currently git commit messages are validated by Jenkins to ensure compliance with the MySensors' standards, a derivative of Chris Beam’s Seven Rules to writing good commit messages. The scope of this change request is to develop a client-side git commit-msg hook that shares the git commit message validation logic implemented on Jenkins.

This has a dependency on Jenkins CI scripts being refactored and added to the git repo.

/cc @fallberg

Updated 16/01/2017 19:13 4 Comments

Improve CI

rmariano/compr
  • Code linting for all code

    • pylint, flake8, with the most strict controls
    • Set max column=79
    • Break the build if the linting does not pass
    • setup code revision for common patterns in code review, automatically. Maybe https://github.com/integrations/sideci can help
  • Tests should ignore the dataset on the run

  • Check that coverage level did not decrease. Fail if it did.
    • setup codecov https://codecov.io/
  • Automate coverage level report per branch, and PR. Link directly in the project main page and documentation.
  • Create a checklist target in Makefile, and separate tests from checklist.
  • Check for security issues and updates automatically. Maybe https://github.com/integrations/src-clr can help
Updated 02/03/2017 08:22 1 Comments

Fork me on GitHub