[Bug 5586] New: I/O operation on a closed file (Windows)

mercurial-bugs at mercurial-scm.org mercurial-bugs at mercurial-scm.org
Sun Jun 4 16:37:21 UTC 2017


https://bz.mercurial-scm.org/show_bug.cgi?id=5586

            Bug ID: 5586
           Summary: I/O operation on a closed file (Windows)
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Windows
            Status: UNCONFIRMED
          Severity: bug
          Priority: normal
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: matt_harbison at yahoo.com
                CC: mercurial-devel at mercurial-scm.org,
                    pierre-yves.david at ens-lyon.org

When running the tests, several fail like so:

--- c:/Users/Matt/Projects/hg/tests/test-obsolete-bundle-strip.t
+++ c:/Users/Matt/Projects/hg/tests/test-obsolete-bundle-strip.t.err
@@ -143,19 +143,43 @@
   #################################

   $ testrevs 'desc("C-A")'
+  $TESTTMP.sh: line 49: $TESTTMP/simple-chain-C-A0
+  -C-A1-relevant-markers.txt: No such file or directory
+  Traceback (most recent call last):
+    File "c:/Users/Matt/Projects/hg/hg", line 45, in <module>
+      mercurial.dispatch.run()
+    File "c:\Users\Matt\Projects\hg\mercurial\dispatch.py", line 86, in run
+      status = (dispatch(req) or 0) & 255
+    File "c:\Users\Matt\Projects\hg\mercurial\dispatch.py", line 190, in
dispatch
+      req.ui.flush()
+    File "c:\Users\Matt\Projects\hg\mercurial\ui.py", line 836, in flush
+      self.fout.flush()
+    File "c:\Users\Matt\Projects\hg\mercurial\windows.py", line 179, in flush
+      return self.fp.flush()
+  ValueError: I/O operation on closed file

Bisected back to here:

The first bad revision is:
changeset:   36265:9df4c2613fca
user:        Pierre-Yves David <pierre-yves.david at octobus.net>
date:        Fri May 26 03:11:53 2017 +0200
summary:     test-obsolete-bundle-strip: test bundling in the first case

Unfortunately, that's only a test change, and I don't have time to dig in
further.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list