Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5,399
    • Issues 5,399
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 592
    • Merge requests 592
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell CompilerGlasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #6061
Closed
Open
Issue created Apr 30, 2012 by Simon Marlow@simonmarDeveloper

threadDelay broken on Windows

There seems to be new breakage in threadDelay on Windows. I noticed conc070 failing in a validate:

=====> conc070(ghci) 191 of 3265 [0, 0, 0]

cd ./concurrent/should_run && 'c:/simonmar/ghc-validate/bindisttest/install   dir/bin/ghc.exe' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-conf -rtsopts  -fno-ghci-history conc070.hs --interactive -v0 -ignore-dot-ghci +RTS -I0.1 -RTS   <conc070.genscript 1>conc070.interp.stdout 2>conc070.interp.stderr

Actual stdout output differs from expected:

--- ./concurrent/should_run/conc070.stdout	2011-08-02 14:43:53 +0100
+++ ./concurrent/should_run/conc070.run.stdout	2012-04-27 10:54:04 +0100
@@ -1 +1 @@
-[ThreadBlocked BlockedOnMVar,ThreadBlocked BlockedOnMVar,ThreadRunning,ThreadFinished]
+[ThreadFinished,ThreadBlocked BlockedOnMVar,ThreadRunning,ThreadFinished]

*** unexpected failure for conc070(ghci)

and strangely if you try threadDelay 1000000 in GHCi it returns immediately.

This test is also failing:

=====> ThreadDelay001(threaded1) 7 of 7 [0, 0, 0]
cd . && 'c:/simonmar/ghc-validate/inplace/bin/ghc-stage2.exe' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-conf -rtsopts  -fno-ghci-history -o ThreadDelay001 ThreadDelay001.hs -threaded -debug   >ThreadDelay001.comp.stderr 2>&1
cd . && ./ThreadDelay001    </dev/null >ThreadDelay001.run.stdout 2>ThreadDelay001.run.stderr
Actual stdout output differs from expected:
--- /dev/null   2012-04-30 11:17:41 +0100
+++ ./ThreadDelay001.run.stdout 2012-04-30 11:17:41 +0100
@@ -0,0 +1,2 @@
+(Mon Apr 30 11:17:29 GMT Daylight Time 2012,Mon Apr 30 11:17:29 GMT Daylight Time 2012,1000000,0,-1000000,-1.0e-6)
+(Mon Apr 30 11:17:29 GMT Daylight Time 2012,Mon Apr 30 11:17:29 GMT Daylight Time 2012,5000000,0,-5000000,-5.0e-6)
*** unexpected failure for ThreadDelay001(threaded1)

Possibly related to the fix for #5865 (closed)

Trac metadata
Trac field Value
Version 7.4.1
Type Bug
TypeOfFailure OtherFailure
Priority highest
Resolution Unresolved
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking