Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pypy pypy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 668
    • Issues 668
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PyPy
  • pypypypy
  • Issues
  • #2978

Closed
Open
Created Mar 25, 2019 by Stefano Rivera@stefanorMaintainer

Avoid timeouts - extra dot in graphlib

Debian has had some issues with pypy builds timing out on some of our slower architectures. Logs. I brought this up on IRC a while ago (probably at least a year), and planned to go digging for some place to insert log.dot() calls. Armin was not very hopeful that I'd find useful places to do this, as we don't want to emit a dot unless the build is actually progressing, and not stuck in a loop.

Anyway, I found 1 place that made a big difference for us. So, I thought I'd share the patch.

I'm happy to test variants of this on MIPS64, which was timing out most "reliably".

I'd say the next most frequent cause of timeouts is in the test harness for cpyext., e.g. log

Attachments: graphlib-dots.patch

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking