Opened 4 years ago

Last modified 6 months ago

#7298 new bug

GHCi is setting stdin/stdout to NoBuffering in runghc when DYNAMIC_GHC_PROGRAMS=YES

Reported by: igloo Owned by:
Priority: high Milestone: 8.2.1
Component: GHCi Version: 7.6.1
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case: ghc-e/should_run/T2228
Blocked By: Blocking:
Related Tickets: #2228 Differential Rev(s):
Wiki Page:

Description

=====> 2228(normal) 6 of 8 [0, 0, 0]
cd . && $MAKE --no-print-directory -s 2228    </dev/null >2228.run.stdout 2>2228.run.stderr
Actual stdout output differs from expected:
--- ./2228.stdout       2011-07-21 12:03:54.000000000 +0100
+++ ./2228.run.stdout   2012-10-05 02:07:04.000000000 +0100
@@ -1,2 +1,2 @@
 BlockBuffering Nothing
-BlockBuffering Nothing
+NoBuffering
*** unexpected failure for 2228(normal)

Change History (7)

comment:1 Changed 3 years ago by igloo

  • Owner igloo deleted

comment:2 Changed 2 years ago by thoughtpolice

  • Milestone changed from 7.8.3 to 7.8.4

Moving to 7.8.4.

comment:3 Changed 20 months ago by thoughtpolice

  • Milestone changed from 7.8.4 to 7.10.1

Moving (in bulk) to 7.10.4

comment:4 Changed 17 months ago by thoughtpolice

  • Cc hvr added
  • Resolution set to wontfix
  • Status changed from new to closed

Closing, since we're moving away from dynamic by default anyway.

comment:5 Changed 17 months ago by thoughtpolice

  • Milestone 7.10.1 deleted

comment:6 Changed 8 months ago by thomie

  • Cc hvr removed
  • Resolution wontfix deleted
  • Status changed from closed to new
  • Summary changed from Test 2228 fails with dynamic-by-default to GHCi is setting stdin/stdout to NoBuffering in runghc when DYNAMIC_GHC_PROGRAMS=YES
  • Test Case set to ghc-e/should_run/T2228

This issue is not fixed. According to ticket:2228#6, runghc shouldn't set stdin/stdout to NoBuffering.

comment:7 Changed 6 months ago by bgamari

  • Milestone set to 8.2.1

While it's a bit late to handle this for 8.0 let's at least try for 8.2.

Note: See TracTickets for help on using tickets.