- 03 May, 2019 1 commit
-
-
Romain Courteaud authored
This is nearly a copy/paste of renderJS error rendering.
-
- 02 May, 2019 5 commits
-
-
Tristan Cavelier authored
While rendering a field_list gadget in non-editable mode, the `text_content` parameter was given only in the first `render` call. /bug #20190204-39AF19 https://nexedijs.erp5.net/#/bug_module/20190204-39AF19 /reviewed-on !860
-
Tristan Cavelier authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Sebastien Robin authored
Before we were using up to 10 testnodes per test suite. Push it to 15 testnodes to have chance to run big test suite (like whole ERP5 tests) in less than 2 hours.
-
- 29 Apr, 2019 3 commits
-
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Georgios Dagkakis authored
/reviewed-on nexedi/erp5!859
-
- 26 Apr, 2019 2 commits
-
-
Romain Courteaud authored
-
Arnaud Fontaine authored
ZODB Components: Use regex to check whether a class of the same name as the Component reference is defined. Until now, there was a very basic string check which didn't handle such cases: class DocumentReferenceAnything(): pass class DocumentReference(): pass => _message_reference_class_not_defined was incorrectly raised as the first class was considered.
-
- 25 Apr, 2019 1 commit
-
-
Sebastien Robin authored
This allows to know the node working on test, thus we can redraft lines when a runTestSuite command fails
-
- 24 Apr, 2019 5 commits
-
-
Sebastien Robin authored
Before we were looking only create date of test results to give priority of work to do for a test nodes. So we had cases where some test suites with medium priority had 5 testnodes, and test suites with high priority having only 3 testnodes. So clearly distribute the work depending on the maximum quantity of testnode we want.
-
Sebastien Robin authored
Right now we have this scenario: - test result line is started - sometimes, runTestSuite fails (like timeout), failure is reported but test result line remains started (we don't know yet which line is associated with testnode) - when a test result line is "started" since more than 4 hours, test result line is redrafted - test can be reexecuted Speed up by removing the need of waiting alarm, by knowing which test result line is executed by which test node, and by redrafting immediately the test result line on test node failure
-
Vincent Pelletier authored
Put auto-generated _getAcquireLocalRoles at the end of mro, removing it from Base. Also, document why it is treated specially here. Also, add _getAcquireLocalRoles methods on a few leaf classes whose instances fake being portal types, without actually being proper document instances. At least, the ones which are detected in unit tests. The proper fix would likely rather be to make them proper document classes, but this carries data migration concerns which go beyond the scope of this regression fix (_getAcquireLocalRoles was not possible to override anymore).
-
Vincent Pelletier authored
-
Vincent Pelletier authored
-
- 23 Apr, 2019 1 commit
-
-
Sebastien Robin authored
This allows code of movement group to still works when they use setter/getters defined by property sheets
-
- 19 Apr, 2019 1 commit
-
-
Sebastien Robin authored
Fully rewrite portal_simulation.mergeDeliveryList to use builders to reconstruct new merged delivery. Add parameter "merge_delivery" to builder. This parameter is used when merge should be done in such a way that movement group at delivery level are ignored
-
- 18 Apr, 2019 1 commit
-
-
Tatuya Kamada authored
For example, testReceiptRecoginition employs numpy matrix calculation methods that try to utilize all the CPU in the computer. This behavior is harmlfull when there are several testReciptRecongnition is running in a testnode which has 40 CPUs.
-
- 17 Apr, 2019 9 commits
-
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
- 16 Apr, 2019 2 commits
-
-
Tristan Cavelier authored
To get the listbox cell value : code was getting last proxy target instead of browsing the full proxy target stack. /bug #20190111-1F86B7B https://nexedijs.erp5.net/#/bug_module/20190111-1F86B7B /reviewed-on !856
-
Sebastien Robin authored
-
- 15 Apr, 2019 2 commits
-
-
Sebastien Robin authored
-
Sebastien Robin authored
-
- 12 Apr, 2019 3 commits
-
-
Sebastien Robin authored
We randomly have unkilled firefox process remaining. Make sure to kill them.
-
Sebastien Robin authored
-
Sebastien Robin authored
-
- 10 Apr, 2019 1 commit
-
-
Xiaowu Zhang authored
-
- 05 Apr, 2019 1 commit
-
-
Romain Courteaud authored
-
- 04 Apr, 2019 2 commits
-
-
Tristan Cavelier authored
/bug #20190204-1BF3A5A https://nexedijs.erp5.net/#/bug_module/20190204-1BF3A5A /reviewed-on nexedi/erp5!848
-
Tristan Cavelier authored
-