Issue6269
Help
Roundup docs
Created on 2017-02-14.10:09:20 by ced, last changed by ced.
| Messages | |||
|---|---|---|---|
| msg50487 (view) | Author: [hidden] (ced)   |
Date: 2019-07-02.08:13:19 | |
Another similar failure: https://drone.tryton.org/tryton/modules.account_payment_clearing/95/21 |
|||
| msg46569 (view) | Author: [hidden] (ced) |
Date: 2019-01-29.08:13:21 | |
Another similar failure: https://drone.tryton.org/tryton/modules.purchase_request/72/18 |
|||
| msg31925 (view) | Author: [hidden] (ced) |
Date: 2017-02-14.19:06:10 | |
I think that monkey-patching in the test Date.today will ensure that the code is actually using it as it should instead of datetime. |
|||
| msg31921 (view) | Author: [hidden] (nicoe) |
Date: 2017-02-14.15:39:47 | |
Isn't it possible to run the scenario using a tool like datefudge or faketime (http://www.code-wizards.com/projects/libfaketime/) ? |
|||
| msg31906 (view) | Author: [hidden] (ced) |
Date: 2017-02-14.10:09:20 | |
The run [1] (which will disappear on relaunch) failed because the scenario run during the midnight. I think we should have the run tests script freeze the today of ir.date and in the scenario we should always use ir.date and not datetime module. [1] https://drone.tryton.org/trypod.tryton.org/tryton/modules.stock_supply/default/b011c4a0c872eee3508565221a48f6c49bb4e3da |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-07-02 08:13:19 | ced | set | messages: + msg50487 |
| 2019-01-29 08:13:21 | ced | set | messages: + msg46569 |
| 2017-02-14 19:06:10 | ced | set | messages: + msg31925 |
| 2017-02-14 15:39:47 | nicoe | set | status: unread -> chatting nosy: + nicoe messages: + msg31921 |
| 2017-02-14 10:12:24 | pokoli | set | nosy: + pokoli |
| 2017-02-14 10:09:20 | ced | create | |
Showing 10 items. Show all history (warning: this could be VERY long)