Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 141
    • Merge requests 141
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !1276

Merged
Created Sep 24, 2020 by Jérome Perrin@jeromeOwner

test_result: try fixing test_04c_startTestSuiteOrderWithManyTestNodes random failure

  • Overview 2
  • Commits 1
  • Pipelines 1
  • Changes 1

This test uses pinDateTime to create an history of test results where tests have been executed in order test suite 1, 2, 3. This is done using this pattern:

  now = DateTime()
  ... # do several things that may actually take more than one second
  self.processTest("test suite 1", "r0=a", node_title="COMP0-Node1")
  self.pinDateTime(now + 1.0/86400)
  self.processTest("test suite 2", "r0=a", node_title="COMP1-Node1")
  self.pinDateTime(now + 2.0/86400)
  self.processTest("test suite 3", "r0=a", node_title="COMP1-Node1")

My guess is that we take "now" too early, and when we add 1 second to this now variable, this may actually be going back in time sometimes, effectively creating test suite 2 before test suite 1.

Assign now to current date after doing all the affectTestSuite calls should solve this.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix/random_failure_testTaskDistribution
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7