Skip to content

Disable benchmarks on CI#2167

Merged
marvinhagemeister merged 1 commit into
masterfrom
benchmark-ci
Dec 3, 2019
Merged

Disable benchmarks on CI#2167
marvinhagemeister merged 1 commit into
masterfrom
benchmark-ci

Conversation

@marvinhagemeister

@marvinhagemeister marvinhagemeister commented Dec 3, 2019

Copy link
Copy Markdown
Member

Running benchmarks on the CI assumes that we always test in the same environment. This doesn't seem to be the case as sometimes the tests are passing and sometimes not. This leads me to conclude that we are assigned a random machine/vm with different specs and workloads.

Fixes build failures in various PRs like #2160 and #2166 .

Running benchmarks on the CI assumes that we always test in the same
environment. This doesn't seem to be the case as sometimes the tests are
passing and sometimes not. This leads me to conclude that we are
assigned a random machine/vm with different specs.
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling a84361f on benchmark-ci into fa224d0 on master.

@JoviDeCroock JoviDeCroock left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed this as well, had to restart a few builds lately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants