An error occurred fetching the project authors.
- 31 Aug, 2016 1 commit
-
-
Sebastien Robin authored
With previous algorithm, work was given to additional test nodes only when: - we were previously below the needed capacity - when another test node was dying Now, as soon as a new test node is added, we move work of overloaded test nodes to idle test nodes. We try to move only test suite using many test nodes to avoid having to wait for building time. This allows to have better distribution of the work with the idea to have more quickly test results. This will avoid cases where we have several testnodes assigned to no work at all. Finally, fixed distribution algorithm to avoid some unfair cases where a test suite might have more test node than another while they both ask for the same number of test nodes.
-
- 01 Jul, 2016 1 commit
-
-
Sebastien Robin authored
Up to now, once all test result lines in draft were processed, test result lines already started where affected to all test nodes. It was designed like this in case the initial affected test node was unable to finish is work (test node or machine could die for various reasons). But having a testnode dying should be rare, thus optimisation should not consider that this happens all the time, even though we must take into account that this could happen. This was leading to cases where a testnode, instead of quiting a test suite to process another was affected a test already affected. So it happened that we loosed one hour of a testnode while it could do much more useful work than repeating the work of another testnode. Thus, consider that testnodes are usually able to process their work, and make testnodes immediately work on another test suite once all tests of a test result are started. Then, run regularly an alarm looking for stuck test to restart them in order to affect work already affected only when required. This change should make the system more reactive when things are working (wich is the majority of time). Not working cases would still finish to work, but in a less reactive way. If we wait urgently for a test result and we see that a test is stuck, there is also possibility to unblock it by hand (if we do not want to wait the alarm).
-
- 04 Apr, 2016 1 commit
-
-
Sebastien Robin authored
-
- 18 Mar, 2016 1 commit
-
-
Sebastien Robin authored
-
- 07 Jan, 2015 1 commit
-
-
Tristan Cavelier authored
- Two methods defined twice with the same code in the same script
-
- 01 Dec, 2014 1 commit
-
-
Jérome Perrin authored
-
- 08 Nov, 2014 1 commit
-
-
Kazuhiko Shiozaki authored
* to quickly setup catalog_full_text table, you can use the following SQL. REPLACE INTO catalog_full_text SELECT uid, title, description FROM catalog; * non fulltext queries like '=abc', '>abc', '%abc%' are supported. * now erp5_full_text_mroonga_catalog is used for unit tests thus I recommend using it instead of erp5_full_text_myisam_catalog. * to migrate existing MyISAM full_text table into Mroonga, you can use the following SQL. ALTER TABLE full_text DROP KEY SearchableText, ENGINE = mroonga, ADD FULLTEXT KEY SearchableText (`SearchableText`) COMMENT 'parser "TokenBigramSplitSymbolAlpha"'; * fulltext search score is no longer provided as (column_name) but now provided as (column_name)__score__. * (category)_title, like source_title, related keys are automatically generated. (category)_description keys as well.
-
- 05 Nov, 2014 1 commit
-
-
Rafael Monnerat authored
-
- 17 Oct, 2014 1 commit
-
-
Rafael Monnerat authored
This parameter has been passed always by the erp5.util implementation. Introduce this parameter makes the API compatible for future implementation with support to scalability tests even if the current code is not ready yet.
-
- 28 Jun, 2014 1 commit
-
-
Sebastien Robin authored
Optimize sorting of list of test suite to be executed by test nodes. We give priority to test suite with older test results. This allows to have test node resources in a more fair way.
-
- 14 Apr, 2014 1 commit
-
-
Benjamin Blanc authored
Conflicts: bt5/erp5_test_result/bt/revision bt5/erp5_test_result/bt/template_document_id_list bt5/erp5_test_result/bt/template_extension_id_list (cherry picked from commit 63c1fc096663f6c96ab61e5acebe2dcbe801dfa5) Conflicts: bt5/erp5_test_result/TestTemplateItem/portal_components/test.erp5.testTaskDistribution.py bt5/erp5_test_result/bt/revision
-
- 05 Aug, 2013 1 commit
-
-
Sebastien Robin authored
-
- 16 Jul, 2013 1 commit
-
-
Sebastien Robin authored
-
- 27 Mar, 2013 1 commit
-
-
Sebastien Robin authored
-
- 20 Feb, 2013 4 commits
-
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-