Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
N NightlyBuild
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • NightlyBuild
  • Issues
  • #7

Closed
Open
Created Jan 10, 2018 by snuverink_j@snuverink_jDeveloper

`last` value can still be evaluated when simulation and reference file have different number of lines

In case the simulation and reference (stat) file have a different number of lines the test is marked as broken. However, in case the last value is asked for the test can still be evaluated.

Evaluating the test in this case would give more information and might even result in a successful test.

Edited Jan 10, 2018 by snuverink_j
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking