| Title | Existing jobs in Perforce may become unusable when the jobspec is changed |
| Status | closed |
| Priority | essential |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | When the P4DTI starts up for the first time, it changes the jobspec without checking to see whether any jobs are present. These jobs may become unusable when the jobspec is changed. |
| Analysis | This is difficult to do; how can the P4DTI know it is being run for the first time. It changes the jobspec every time it starts up. Perhaps we should tell people to run refresh.py before run.py? |
| How found | customer |
| Evidence | <http://info.ravenbrook.com/mail/2001/02/19/23-44-04/0.txt>
This is Perforce job 5003. |
| Observed in | 0.4.2 |
| Introduced in | 0.4.0 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 7 |
| Created by | Gareth Rees |
| Created on | 2001-02-20 13:01:22 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:24:50 |
| History | 2001-02-20 GDR Created. |