• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

PragTob / benchee
95%
master: 94%

Build:
Build:
LAST BUILD BRANCH: relative-statistics
DEFAULT BRANCH: master
Repo Added 05 Feb 2017 09:58AM UTC
Files 38
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH parallel-bug
branch: parallel-bug
CHANGE BRANCH
x
Reset
  • parallel-bug
  • 0-runtime-handling
  • 0.10.0
  • 0.11.0
  • 0.12
  • 0.12.0
  • 0.12.1
  • 0.12.1-release
  • 0.13
  • 0.13-updates
  • 0.13.0
  • 0.13.1
  • 0.13.2
  • 0.13.2-cherry-pick
  • 0.14.0
  • 0.7.0
  • 0.8.0
  • 0.9.0
  • 1.5.0-rc2-update
  • 1.6-rc0
  • Bessels-Correction
  • Issue-123
  • Issue-188
  • Issue-208
  • Issue-259
  • Issue-51
  • Issue-53
  • Issue-68
  • PragTob-patch-1
  • account-for-old-generation-memory-measurement
  • add-benchee_markdown-formatter
  • add-percentile
  • add-percentiles
  • after-scenario-inputs
  • application-inflection
  • appveyor
  • before-after-each-simple
  • before-each-inputs
  • before_after_scenarios
  • before_scenario_altering_input
  • behaviour-reuse
  • calculate-memory-stats
  • changelog-update
  • changelog-updates
  • check-in-tool-versions
  • config-types
  • conversion-units
  • coveralls-try
  • credo
  • deprecations
  • deps-up
  • deps-updates
  • dialyzer-weirdness
  • doc-it
  • drop-1.2-support-cleanups
  • drop-negative-memory-measurements
  • dry-run
  • easy-updates
  • eliminate-duplicated-benchmarking-messages
  • elixir-1-5-2
  • elixir-1.5
  • elixir-1.5.1
  • elixir-1.6-final
  • elixir-1.6.3
  • elixir-1.7.0-rc1
  • elixir-1.8
  • elixir-erlang-updates
  • elixir-update
  • erlang-module-style
  • estimated-run-times-fix
  • exact-elixir-version
  • exguard
  • fix-race-condition-with-tracer
  • flaky-overhead-test
  • format-bigger-floats
  • format-samples
  • format-test
  • formatter-definition
  • formatter-options-closer
  • formatting
  • formatting-1
  • formatting-2
  • formatting-3
  • formatting-everything
  • formatting-everything-2
  • formatting-everything-3
  • formatting-everything-4
  • formatting-everything-5
  • formatting-everything-6
  • formatting-everything-7
  • function-call-overhead
  • gfvcastro-update-to_filename-pattern
  • gigabyte-binary-interpretation
  • hmm-updates
  • hooks-documentation
  • hooks-documentation-alt
  • inchex-update
  • issue-191
  • jose-erlang-compatibility
  • joshnuss-atom-input-keys
  • length-sample
  • lwalter-master
  • macro-tests
  • master
  • measure-memory-3
  • memory-again
  • memory-breaker-integreation-test
  • memory-documentation
  • memory-format-crash
  • memory-formatting-bug
  • memory-measurement-issues
  • memsup-get-stystem-memory
  • mention-slack
  • moaree-updates
  • nano-seconds
  • new-elixir-and-erlang
  • no-prying
  • parallel-bug-alternative
  • pass-values-to-after
  • pipeify
  • random-improvements
  • readme-adjustments
  • relative-statistics
  • remove-not-always-working-cpu-speed-test
  • safe-coveralls
  • scale-printed-configuration-times
  • scenario-data-processed
  • scenario-first-class
  • separate-memory-and-runtime-measurement
  • simplify-measure-memory
  • sort-scenarios
  • statistics-mode
  • statistics-timeout
  • store-and-load-documentation
  • store-previous-runs
  • tagged-save-numbers
  • test-general-mhz-case
  • travis-do-you-master
  • travis-vm-fix-dialyzer
  • trying-to-figure-out-nil-problem-in-benchee-csv
  • type-checking
  • unit-scaling-top-level-option
  • update-deep-merge
  • update-travis
  • update-versions
  • updates
  • updatessss
  • upgrades
  • warn-memory-otp-18
  • warnings-as-errors
  • zachdaniel-fix-tag-name

pending completion
733

push

travis-ci

devonestes
Refactor where we're running things in parallel

The original fix I had for this was kind of hacky, but this moves the
parallelization down to just where we're measuring runtimes. This
should actually be slightly more efficient when we're running
benchmarks in parallel (and less buggy) since before we were running
the `before_scenario` and `after_scenario` hooks before each _instance_
of the benchmark (when running in parallel). Now we run them only once
before each scenario, and each scenario itself is run in parallel.

9 of 9 new or added lines in 1 file covered. (100.0%)

404 of 426 relevant lines covered (94.84%)

16369.71 hits per line

Relevant lines Covered
Build:
Build:
426 RELEVANT LINES 404 COVERED LINES
16369.71 HITS PER LINE
Source Files on parallel-bug
  • List 0
  • Changed 7
  • Source Changed 1
  • Coverage Changed 7
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
733 parallel-bug Refactor where we're running things in parallel The original fix I had for this was kind of hacky, but this moves the parallelization down to just where we're measuring runtimes. This should actually be slightly more efficient when we're running ... push 09 Jan 2018 10:02AM UTC devonestes travis-ci pending completion  
731 parallel-bug Refactor where we're running things in parallel The original fix I had for this was kind of hacky, but this moves the parallelization down to just where we're measuring runtimes. This should actually be slightly more efficient when we're running ... push 09 Jan 2018 09:52AM UTC devonestes travis-ci pending completion  
727 parallel-bug Fix bug running tests in parallel benchmarks If you were running benchmarks in parallel, you would see results for each parallel process you were running. So, if you were running two jobs, and setting your configuration to `parallel: 2`, you woul... push 08 Jan 2018 08:13PM UTC devonestes travis-ci pending completion  
725 parallel-bug Fix bug running tests in parallel benchmarks If you were running benchmarks in parallel, you would see results for each parallel process you were running. So, if you were running two jobs, and setting your configuration to `parallel: 2`, you woul... push 08 Jan 2018 09:19AM UTC devonestes travis-ci pending completion  
723 parallel-bug Fix bug running tests in parallel benchmarks If you were running benchmarks in parallel, you would see results for each parallel process you were running. So, if you were running two jobs, and setting your configuration to `parallel: 2`, you woul... push 08 Jan 2018 09:12AM UTC devonestes travis-ci pending completion  
722 parallel-bug Fix bug running tests in parallel benchmarks If you were running benchmarks in parallel, you would see results for each parallel process you were running. So, if you were running two jobs, and setting your configuration to `parallel: 2`, you woul... push 08 Jan 2018 09:09AM UTC devonestes travis-ci pending completion  
See All Builds (980)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc