Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W wendelin
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • wendelin
  • Merge requests
  • !175

Merged
Created May 30, 2025 by Xiaowu Zhang@xiaowu.zhangDeveloper

fix random failed configurator tests

  • Overview 4
  • Commits 1
  • Changes 1

While checking wendelin test result, i noticed that configurator test failed from time to time, like this test result

It happaned when all the configurator tests run at one test node.

In the test result above, all configurator tests were run at rapidspace-testnode-007-3Nodes-ERP5PROJECT4

Here are extract of the logs, we can see for instance home unit_test.3

It run firstly erp5_wendelin_configurator:testWendelinConfigurator, then it loaded data created previous to run erp5_wendelin_configurator:testWendelinConfiguratorSetupDataSample

But since the site was already configured by previous test, it will not configurated again, thus we have one test failed

2025-05-23 16:23:49,625 INFO     runTestSuite: $ runUnitTest xxx --instance_home **unit_test.3** --load --save --with_wendelin_core erp5_wendelin_configurator:testWendelinConfigurator

2025-05-23 16:31:19,310 INFO     runTestSuite: $ runUnitTest xxx --instance_home **unit_test.1** --load --save --with_wendelin_core erp5_wendelin_configurator:testWendelinConfiguratorSetupDataLakeAndSecurityModel

2025-05-23 16:35:10,525 INFO     runTestSuite: $ runUnitTest xxx --instance_home **unit_test.3** --load --save --with_wendelin_core erp5_wendelin_configurator:testWendelinConfiguratorSetupDataSample

2025-05-23 16:35:25,498 INFO     runTestSuite: $ runUnitTest xxx --instance_home **unit_test.2** --load --save --with_wendelin_core erp5_wendelin_configurator:testWendelinConfiguratorSetupDataNotebook

To fix the random configurator test, i propose to not use load&save for it

@Tyagov what do you think ?

Edited Jun 05, 2025 by Xiaowu Zhang
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix_configurator_test
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7