Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mjtest-tests
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IPDSnelting
  • mjtest-tests
  • Merge Requests
  • !56

Merged
Opened Jan 15, 2019 by ufebl@ufeblContributor

Move benchmarks into big folder

  • Overview 2
  • Commits 1
  • Changes 13

The benchmarks need a longer time to run, so we might not want to run them in every push for our CI. If they are placed in the big folder they are only run if you supply the --all-exec-tests flag to mjtest.

This merge requests also renames the java files to input.java, so that the supplied inputc files are actually read.
It also provides output files for all tests as running the BigTensorProduct test with Java to calculate the reference output leads to a OutOfMemory error on our CI machine.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: IPDSnelting/mjtest-tests!56
Source branch: benchmarks-big-folder

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.