This project is mirrored from https://*****@github.com/hermitcore/uhyve.git. Pull mirroring updated .
  1. 02 Feb, 2021 1 commit
  2. 29 Jan, 2021 2 commits
    • bors[bot]'s avatar
      Merge #76 · a4139de3
      bors[bot] authored
      
      
      76: CI: Improve codecov project status r=stlankes a=jschwe
      
      Don't fail the `codecov/project` status if coverage drops by at most 1%. 
      Since some lines in uhyve are sometimes compiled, but not covered, and sometimes not compiled at all, there
      is a certain base fluctuation regarding the "missing" lines.
      Co-authored-by: default avatarjschwe <55576758+jschwe@users.noreply.github.com>
      a4139de3
    • jschwe's avatar
      CI: Improve codecov project status · e0de02b7
      jschwe authored
      Don't fail the `codecov/project` status if coverage drops by at most 1%. 
      Since some lines in uhyve are sometimes compiled, but not covered, and sometimes not compiled at all, there
      is a certain base fluctuation regarding the "missing" lines.
      e0de02b7
  3. 27 Jan, 2021 2 commits
  4. 26 Jan, 2021 1 commit
    • bors[bot]'s avatar
      Merge #72 · b801a104
      bors[bot] authored
      72: Bump criterion from 0.3.3 to 0.3.4 r=jbreitbart a=dependabot[bot]
      
      Bumps [criterion](https://github.com/bheisler/criterion.rs) from 0.3.3 to 0.3.4.
      <details>
      <summary>Changelog</summary>
      <p><em>Sourced from <a href="https://github.com/bheisler/criterion.rs/blob/master/CHANGELOG.md">criterion's changelog</a>.</em></p>
      <blockquote>
      <h1>Changelog</h1>
      <p>All notable changes to this project will be documented in this file.</p>
      <p>The format is based on <a href="http://keepachangelog.com/en/1.0.0/">Keep a Changelog</a>
      and this project adheres to <a href="http://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p>
      <h2>[Unreleased]</h2>
      <h3>Added</h3>
      <ul>
      <li>Added support for benchmarking async functions</li>
      <li>Added <code>with_output_color</code> for enabling or disabling CLI output coloring programmatically.</li>
      </ul>
      <h3>Fixed</h3>
      <ul>
      <li>Criterion.rs will now give a clear error message in case of benchmarks that take zero time.</li>
      <li>Added some extra code to ensure that every sample has at least one iteration.</li>
      <li>Added a notice to the <code>--help</code> output regarding &quot;unrecognized option&quot; errors.</li>
      <li>Increased opacity on violin charts.</li>
      <li>Fixed violin chart X axis not starting at zero in the plotters backend.</li>
      <li>Criterion.rs will now automatically detect the right output directory.</li>
      </ul>
      <h3>Deprecated</h3>
      <ul>
      <li><code>Criterion::can_plot</code> is no longer useful and is deprecated pending deletion in 0.4.0.</li>
      <li><code>Benchmark</code> and <code>ParameterizedBenchmark</code> were already hidden from documentation, but are now
      formally deprecated pending deletion in 0.4.0. Callers should use <code>BenchmarkGroup</code> instead.</li>
      <li><code>Criterion::bench_function_over_inputs</code>, <code>Criterion::bench_functions</code>, and <code>Criterion::bench</code> were
      already hidden from documentation, but are now formally deprecated pending deletion in 0.4.0.
      Callers should use <code>BenchmarkGroup</code> instead.</li>
      <li>Three new optional features have been added; &quot;html_reports&quot;, &quot;csv_output&quot; and
      &quot;cargo_bench_support&quot;. These features currently do nothing except disable a warning message at
      runtime, but in version 0.4.0 they will be used to enable HTML report generation, CSV file
      generation, and the ability to run in cargo-bench (as opposed to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a>).
      &quot;cargo_bench_support&quot; is enabled by default, but &quot;html_reports&quot; and &quot;csv_output&quot;
      are not. If you use Criterion.rs' HTML reports, it is recommended to switch to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a>.
      If you use CSV output, it is recommended to switch to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a> and use the
      <code>--message-format=json</code> option for machine-readable output instead. A warning message will be
      printed at the start of benchmark runs which do not have &quot;html_reports&quot; or &quot;cargo_bench_support&quot;
      enabled, but because CSV output is not widely used it has no warning.</li>
      </ul>
      </blockquote>
      </details>
      <details>
      <summary>Commits</summary>
      <ul>
      <li>See full diff in <a href="https://github.com/bheisler/criterion.rs/commits">compare view</a></li>
      </ul>
      </details>
      <br />
      
      
      [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=criterion&package-manager=cargo&previous-version=0.3.3&new-version=0.3.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores
      
      )
      
      Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
      
      [//]: # (dependabot-automerge-start)
      [//]: # (dependabot-automerge-end)
      
      ---
      
      <details>
      <summary>Dependabot commands and options</summary>
      <br />
      
      You can trigger Dependabot actions by commenting on this PR:
      - `@dependabot rebase` will rebase this PR
      - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
      - `@dependabot merge` will merge this PR after your CI passes on it
      - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
      - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
      - `@dependabot reopen` will reopen this PR if it is closed
      - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
      - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
      - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
      - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
      
      
      </details>
      Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
      b801a104
  5. 25 Jan, 2021 1 commit
  6. 24 Jan, 2021 4 commits
  7. 23 Jan, 2021 14 commits
  8. 22 Jan, 2021 11 commits
  9. 20 Jan, 2021 1 commit
    • bors[bot]'s avatar
      Merge #58 · 4c1baebb
      bors[bot] authored
      
      
      58: Add code Coverage reports r=stlankes a=jschwe
      
      This is #53 again. Creating this again, so that bors works.
      
      This PR mainly adds a script that automates test coverage report generation.
      To generate the report the binaries is instrumented by setting the RUSTFLAG -Zinstrument-coverage which enables source-based coverage.
      I've tested and this works for both unit and doctests (Master currently does not have any doctests, I verified it with a doctest I added locally).
      
      The test coverage generated is specific to the architecture, i.e. the coverage report generated on a Linux machine will not consider any of the code which is for macOS and it won't appear in the reports.
      However codecov.io automatically merges reports from different architectures, so the report, that the codecov bot will hopefully link below, should show a complete picture.
      Co-authored-by: default avatarJonathan Schwender <schwenderjonathan@gmail.com>
      Co-authored-by: default avatarjschwe <55576758+jschwe@users.noreply.github.com>
      4c1baebb
  10. 19 Jan, 2021 3 commits
    • Stefan Lankes's avatar
      increase version number · f8cca7a4
      Stefan Lankes authored
      f8cca7a4
    • bors[bot]'s avatar
      Merge #64 · 8f089ad3
      bors[bot] authored
      
      
      64: Added instrument feature using rftrace r=stlankes a=jbreitbart
      
      Added `instrument` feature, which is disabled by default. It only works
      if uhyve is compiled with `-Z instrument-mcount`. Furthermore I removed
      the std::process::exit() call from uhyvelib so it is possible to write
      the trace. The return value is not returned from `VirtualCPU::run()`.
      
      Note that using rftrace may not be the best tool to trace uhyve as there
      are various other tools available on a modern desktop OS, but can be
      used to trace RustyHermit and using the same tool simplifies everything
      a bit.
      Co-authored-by: default avatarJens Breitbart <jbreitbart@gmail.com>
      8f089ad3
    • Jens Breitbart's avatar
      85135005