Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27139
Closed (moved) (moved)
Open
Issue created Aug 14, 2018 by teor@teor

macOS i386 fails time unit tests

circuitmux/compute_ticks: [forking] 
  FAIL src/test/test_circuitmux.c:109: assert(rem OP_LT .150000001): 0.1505 vs 0.15
  [compute_ticks FAILED]
mainloop/update_time_jumps: [forking] 
  FAIL src/test/test_mainloop.c:115: expected log to not contain entries  Captured logs:
    1. notice: "Your system clock just jumped 1800 seconds forward; assuming established circuits no longer work.\n"

  [update_time_jumps FAILED]

Should we set up macOS i386 CI to detect issues like this? Or should we remove macOS i386 from our supported platforms? (Apple won't support i386 in the next macOS, so in ~3 years time, we won't need to support it.)

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