Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #765

Closed
Open
Created Jul 07, 2022 by Elizaveta Lutsenko@LizLutsenkoOwner

"ValueError: I/O operation on closed file" in Github test runner

Created by: gkirgizov

Several PRs on github are failing now because of this error.

Seems related to these problems in pytest

  • https://github.com/pytest-dev/pytest/issues/5502#issuecomment-526348052
  • https://github.com/pytest-dev/pytest/issues/3344

UPD: Problem is because pytest tampers with stdout/stderr. Anything that uses them, can cause this problem (logging, print, tqdm in our case)

UPD2: Now the only problem is tqdm that must be disabled completely in certain tests

UPD3: more related things

  • https://github.com/pytest-dev/pytest/issues/14#issuecomment-521577819
  • possibly this also: https://github.com/JonathanCasey/asana_extensions/issues/51 (there's usage of capsys in one test)
Assignee
Assign to
Time tracking