- 08 May, 2017 1 commit
-
-
Arnaud Fontaine authored
1. 'Solve Divergences' action: => Display Delivery_viewSolveDivergenceDialog.listbox: -> Delivery_getSolverDecisionList -> Delivery_getSolverProcess => create Solver Process in 'draft' state and build Solver Decisions. 2. Clicking 'Update' button updates Solver Decisions. 3. Click 'Solve Divergences' button after either 'Adopt Prevision' or 'Accept Decision'. => SolverProcess.solve(): Solver Process transit to 'solving' state and 'solve' Activity is created. Before this Activity is executed, user can still select 'Solve Divergences' action and this will create another 'Solver Process' as the current one is not in 'draft' state anymore. Moreover, another user can still 'Adopt Prevision' (while the first user selected 'Accept Decision') and this will be actually be applied despite the first user choice. Instead, create Solver Process when transiting to 'diverged' state and do not display 'Solve Divergences' button nor allow access to 'Solve Divergences Dialog' (Delivery_viewSolveDivergenceDialog) if there is a Solver Process in 'solving' state.
-
- 27 Apr, 2017 1 commit
-
-
Tristan Cavelier authored
-
- 25 Apr, 2017 2 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
- 24 Apr, 2017 1 commit
-
-
Vincent Pelletier authored
Because of ERP5Type.UnrestrictedMethod, 'System Processes' can own objects. Such objects can be proxy-role'd scripts, and proxy-role mechanism triggers many users look-ups (each time security is evaluated, which is virtually every getattr). Each such lookup will do a query for 'System Processes' user, which will (hopefully) find nothing anyway. So special-case 'System Processes' when looking by user_id by skipping the search altogether (enforcing the inability to locate this user, consistently with Zope assumptions, and consistently with previous behaviour).
-
- 21 Apr, 2017 4 commits
-
-
Sebastien Robin authored
The code was not working as expected when we had several test nodes with same name (which should not happen). So add a timestamp in the title.
-
Sebastien Robin authored
-
Sebastien Robin authored
test_result: fixed random issues where test result was staying confirmed while all tests were finished When two test results line were stopped in parallel, both transactions were thinking that there was still one ongoing test line, thus none of them were setting the test result in stopped. Use activities instead of serialization to avoid having testnode getting conflict errors.
-
Vincent Pelletier authored
This makes a difference for SQLDict as not all messages are accepted for insertion.
-
- 20 Apr, 2017 14 commits
-
-
Julien Muchembled authored
Firefox and Xvfb aren not provided by the tested SR, but rather by a separate SR that is installed by the testnode.
-
Sebastien Robin authored
-
Sebastien Robin authored
Charting libraries are better within iframe to avoid enabling too permissive Content Security Policy globally
-
Sebastien Robin authored
-
Xiaowu Zhang authored
Fix error display after save Fix parameters not recognized Fix python linting the same way as ERP5 Script Python
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
Add PortalType field to distinguish different types of Python Scripts, add referencence and use source code editor
-
Klaus Wölfel authored
-
Klaus Wölfel authored
-
- 19 Apr, 2017 2 commits
-
-
Jérome Perrin authored
We could not find a portable way to use verifyElementPositionRangeTop. See internal discussion `[test][erp5] update selenium test` for more details.
-
Jérome Perrin authored
-
- 18 Apr, 2017 12 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
In addition to TypeEror when a 'date' is given, this also accepts duration=0.
-
Łukasz Nowak authored
If Test Result is associated with Test Node and thus distributor, and distributor defines process timeout use this timeout to now when to restart test lines. This is useful to avoid needless restart of tests running on nodes related to long time outing distributors. Otherwise fallback to default.
-
Łukasz Nowak authored
This link allows to navigate from Test Result via its Test Result Node to Test Node and distributor related to given Test Result. Note: It happens only, if client will do subscribeNode before calling createTestResult.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
This is accompanying commit to "erp5_test_result: stop affecting last remaining tests to all test nodes", where alarms redrafts running tests for long running nodes. In case of very long running test nodes, to which support is introduced in this work, it is acceptable situation that test will get redrafted and shall be stopped.
-
Łukasz Nowak authored
Unfinished test (test_18_checkConfigurationGenerationERP5ScalabilityDistributor) uses return value of subscribeNode and assumes it is ERP5 object. This work changes return value of subscribeNode to JSON object, following startTestSuite return value, thus rendering this test failure. As test is unfinished, non asserting part has been commented out.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Also if process_timeout is available in received configuration setup process_manager with transmitted value. Backward compatibility is assured, that if no process_timeout is provided, nothing is being updated. Also process_timeout not set on master (the default), will not change local default.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Extend subscribeNode to send configuration provided by user.
-
Łukasz Nowak authored
ERP5ProjectUnitTestDistributor allows to define maximum process timeout of testnodes attached to it.
-
- 17 Apr, 2017 1 commit
-
-
Nicolas Wavrant authored
Sending mode is set by user when printing the DSN report
-
- 14 Apr, 2017 2 commits
-
-
Cédric Le Ninivin authored
-
Romain Courteaud authored
-