Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
why3
why3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 120
    • Issues 120
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Why3
  • why3why3
  • Issues
  • #528

Closed
Open
Opened Jan 15, 2021 by Guillaume Melquiond@melquionOwner

Ugly output of why3replay

The new layout is quite ugly:

Replaying multiprecision/mpz_add ... FAILED (ret code=1): 1/2 (replay failed)
   goal 'wmpz_add'vc.436.0.0', prover 'Alt-Ergo 2.3.0': Prover result is:
                                                          timeout (7.00s). instead of 
Prover result is: valid (3.24s, 1328 steps). (timelimit=5, memlimit=2000, steplimit=0)
Replaying tests-provers/div ... FAILED (ret code=1): 13/25 (replay failed)
   goal 'smoke2', prover 'Vampire 0.6': Prover result is: unknown (Time out)
                                          (0.39s). instead of Prover result
                                                                is: timeout
                                                                (1.00s). (timelimit=1, memlimit=1000, steplimit=0)

For comparison, here is the old layout:

 Replaying multiprecision/div ... FAILED (ret code=1): 12/13 (replay failed)
   goal 'div3by2_inv'vc.16.0.0.0', prover 'CVC4 1.6': Timeout (2.00s, 336724 steps) instead of Valid (1.19s, 76304 steps) (timelimit=1, memlimit=1000, steplimit=0)
   goal 'div3by2_inv'vc.25', prover 'CVC4 1.5': Timeout (5.00s, 773971 steps) instead of Valid (1.28s, 74869 steps) (timelimit=5, memlimit=1000, steplimit=0)

Presumably, this was caused by c7d413b1

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
1.4.0
Milestone
1.4.0
Assign milestone
Time tracking
None
Due date
None
Reference: why3/why3#528