Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P pypocketfft
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Martin Reinecke
  • pypocketfft
  • Issues
  • #14
Closed
Open
Issue created Sep 03, 2020 by Martin Reinecke@mtrOwner

More interesting OSX issues

I have a CI setup for tests on OSX for the ducc package, which contains an almost verbatim copy of pypocketfft's threading functionality. One thing I learned was that in certain circumstances the C++ compiler defines some functionality macros, despite the functionality not being available (see https://travis-ci.com/github/litebird/ducc/jobs/380712386).

Also it appears possible to create deadlocks with the new threading implementation on OSX (see the other recent failed builds at https://travis-ci.com/github/litebird/ducc/builds). It's quite possible that I broke something when I adjusted the threading code for ducc, but on the other hand the changes were quite minimal. @g-peterbell, if you have an idea what could be going wrong and/or think that the pypocketfft might also be vulnerable to this, please chime in!

Assignee
Assign to
Time tracking