• 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 memory-again
branch: memory-again
CHANGE BRANCH
x
Reset
  • memory-again
  • 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-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
  • 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
1169

Pull #244

travis-ci

web-flow
Change how we're dealing with the return value

This way we're not executing the function twice, and we don't need to
allocate an extra tuple for the `send` to the parent process. It's a
little dangerous, but not really.
Pull Request #244: Remove any bindings to any data allocated during measurement

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

573 of 602 relevant lines covered (95.18%)

15751.47 hits per line

Relevant lines Covered
Build:
Build:
602 RELEVANT LINES 573 COVERED LINES
15751.47 HITS PER LINE
Source Files on memory-again
  • List 0
  • Changed 21
  • Source Changed 6
  • Coverage Changed 21
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
1169 memory-again Change how we're dealing with the return value This way we're not executing the function twice, and we don't need to allocate an extra tuple for the `send` to the parent process. It's a little dangerous, but not really. Pull #244 03 Aug 2018 12:57PM UTC web-flow travis-ci pending completion  
1168 memory-again Change how we're dealing with the return value This way we're not executing the function twice, and we don't need to allocate an extra tuple for the `send` to the parent process. It's a little dangerous, but not really. push 03 Aug 2018 12:57PM UTC devonestes travis-ci pending completion  
1161 memory-again Change how we're dealing with the return value This way we're not executing the function twice, and we don't need to allocate an extra tuple for the `send` to the parent process. It's a little dangerous, but not really. Pull #244 03 Aug 2018 11:24AM UTC web-flow travis-ci pending completion  
1160 memory-again Change how we're dealing with the return value This way we're not executing the function twice, and we don't need to allocate an extra tuple for the `send` to the parent process. It's a little dangerous, but not really. push 03 Aug 2018 11:22AM UTC devonestes travis-ci pending completion  
1154 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... push 02 Aug 2018 12:36PM UTC devonestes travis-ci pending completion  
1155 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... Pull #244 02 Aug 2018 12:36PM UTC web-flow travis-ci pending completion  
1153 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... Pull #244 02 Aug 2018 12:29PM UTC web-flow travis-ci pending completion  
1152 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... push 02 Aug 2018 12:23PM UTC devonestes travis-ci pending completion  
1151 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... Pull #244 02 Aug 2018 12:17PM UTC web-flow travis-ci pending completion  
1150 memory-again Remove any bindings to any data allocated during measurement This will ensure that we're collecting _only_ data that is allocated as part of the execution of the function we're trying to benchmark. The downside is that we end up running the funct... push 02 Aug 2018 12:17PM 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