Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NVIDIA/cuda-quantum
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: c4ac946fa39e96bb67fa48eb271af2149c1375a4
Choose a base ref
...
head repository: NVIDIA/cuda-quantum
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 61bfac99f9901198098296dd2ea03743e024e9d3
Choose a head ref
  • 6 commits
  • 143 files changed
  • 2 contributors

Commits on Feb 16, 2024

  1. [test] Quick fix: precision issue with f32 backend (#1248)

    @boschmitt
    boschmitt authored Feb 16, 2024
    Configuration menu
    Copy the full SHA
    2b7cfea View commit details
    Browse the repository at this point in the history

  2. [testing] Reorganize the test structure. 

    The various directories should be organized as follows:

test - these are small regression tests that can be run very quickly and test
  small combinations of functionality to prevent regressions. does not use
  gtest framework, but rather FileCheck and friends.

unittests - similar to test, but fixating on one particular "unit". tests the
  unit's boundaries, limits, etc. to make sure that a particular encapsulated
  blob of computation (the unit) works as advertised. uses gtest framework.

targettests - not like the 2 above. these are end-to-end tests that might take
  a long time to run but test a whole 9 yards of functionality. so if you
  wanted to run a game of quantum nethack, it would go here.

  note: eventually these tests should be executable out-of-tree so that
  installations of cuda quantum can be tested sans source code.

python/tests - these should be folded into the above testing
  infrastructure.
    @schweitzpgi
    schweitzpgi committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    86072ed View commit details
    Browse the repository at this point in the history

  3. Workaround obvious code reference for the spelling checker.

    @schweitzpgi
    schweitzpgi committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    d65f624 View commit details
    Browse the repository at this point in the history

  4. Fix breakage in clang-format being overly applied.

    @schweitzpgi
    schweitzpgi committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    0684e8e View commit details
    Browse the repository at this point in the history

  5. Add python for good measure.

    @schweitzpgi
    schweitzpgi committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    2a626b7 View commit details
    Browse the repository at this point in the history

  6. Add a README.txt to explain the testing organization.

    @schweitzpgi
    schweitzpgi committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    61bfac9 View commit details
    Browse the repository at this point in the history
Loading