mis-scheduled tasks

Status: Beta

Brought to you by: mreithinger, p_christeas

#29 mis-scheduled tasks

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2012-09-14

Created: 2007-11-05

Creator: Iván Lloro

Private: No

See attached test cases for bug related to mis-scheduled tasks and the expected behaviour.

Regards,

Discussion

Iván Lloro - 2007-11-05

3 bug cases.

bugcases.tgz

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Chart of test case bug.py

bug.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Logged In: YES
user_id=501651
Originator: YES

File Added: bug.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Logged In: YES
user_id=501651
Originator: YES

File Added: bug2.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Chart of test case bug2.py

bug2.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Logged In: YES
user_id=501651
Originator: YES

File Added: bug2.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Chart of test case bug3.py

bug3.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2007-11-06

Logged In: YES
user_id=501651
Originator: YES

File Added: bug3.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Reithinger - 2008-01-06

Logged In: YES
user_id=931150
Originator: NO

bug2.py is not a bug: you have to define an extra calendar for the parent task.
The rest is fixed

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

I am reopening this bug report. I believe the bugs here described are closely related to this bug thread and not really new ones.

The original case examples where only 2 chained tasks where scheduled are corrected and working as expected in the last faces version (0.11.7). Nevertheless, the fix seems to fail when there are more than 2 chained tasks. Tasks are scheduled to last more than in reality if using the SMART algorithm (see attached bug6).

Besides, it seems resource use conflicts are not correctly solved in these corner cases (see bug4 [using SMART] and bug5 [using STRICT]).
File Added: bug4.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Chart of test case bug4.py

bug4.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

File Added: bug4.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Bug4 test case

bug4.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Chart of test case bug5.py

bug5.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

File Added: bug5.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Bug5 test case

bug5.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

File Added: bug5.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Chart of test case bug6.py

bug6.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

File Added: bug6.pdf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

File Added: bug6.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Bug6 test case

bug6.py

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Iván Lloro - 2008-02-18

Logged In: YES
user_id=501651
Originator: YES

The original case examples where only 2 chained tasks where scheduled >are corrected and working as expected in the last faces version >(0.11.7). Nevertheless, the fix seems to fail when there are more >than 2 chained tasks. Tasks are scheduled to last more than in >reality if using the SMART algorithm (see attached bug6).

Editing my own bug report as the actual bug is not what described there. What can be seen at bug6.py is that a task scheduled to be done on just one weekend is really scheduled by faces to take 2 weekends when a "monday to friday" task overflows to next week. In the example bug6.py this is forced by scheduling a 6-day task.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.