Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub workflow for running unit tests for MKL backend on CPU #483

Merged
merged 7 commits into from
May 16, 2024

Commits on May 11, 2024

  1. pr testing

    rscohn2 committed May 11, 2024
    Configuration menu
    Copy the full SHA
    eacfa2b View commit details
    Browse the repository at this point in the history

Commits on May 13, 2024

  1. add cpu to job name

    rscohn2 committed May 13, 2024
    Configuration menu
    Copy the full SHA
    9d50241 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ffcfe27 View commit details
    Browse the repository at this point in the history

Commits on May 14, 2024

  1. Configuration menu
    Copy the full SHA
    ff0fa90 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    3051c03 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    a32e30e View commit details
    Browse the repository at this point in the history

Commits on May 16, 2024

  1. Apply suggestions from code review

    verbose logging and serial test execution for more readable logs. build time dominates so parallel test is less important.
    
    Co-authored-by: Dai-Ni Hsieh <[email protected]>
    rscohn2 and dnhsieh-intel authored May 16, 2024
    Configuration menu
    Copy the full SHA
    1acabc9 View commit details
    Browse the repository at this point in the history