Opened 10 years ago

Last modified 3 days ago

#797 new bug

nofib tests fail on Windows due to different EOL convention in output files

Reported by: simonmar Owned by:
Priority: normal Milestone: 6.6
Component: NoFib benchmark suite Version: 6.4.1
Keywords: Cc:
Operating System: Windows Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Change History (5)

comment:1 Changed 9 years ago by igloo

  • Owner set to igloo

comment:2 Changed 9 years ago by igloo

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

comment:3 Changed 7 years ago by simonmar

  • Architecture changed from Unknown to Unknown/Multiple

comment:4 Changed 6 years ago by simonmar

  • difficulty changed from Easy (1 hr) to Easy (less than 1 hour)

comment:5 Changed 3 days ago by thomie

  • Description modified (diff)
  • Owner igloo deleted
  • Resolution fixed deleted
  • Status changed from closed to new
  • Type of failure set to None/Unknown

NoFib on Windows fails for me using ghc-8.1 with expected stdout not matched by reality. Seems to be a line ending issue.

This is the command I try to run, following instructions from Building/RunningNoFib:

cd nofib
make boot
make exeext=.exe

The benchmark spectral/ansi also fails inexplicably.

Last edited 3 days ago by thomie (previous) (diff)
Note: See TracTickets for help on using tickets.