Opened 19 years ago
Closed 18 years ago
#259 closed defect (fixed)
A job's progress doesn't get upadated when a job is executing in another virutal machine
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | minor | Milestone: | BASE 2.0 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
Probably due to caching of the job information by the second-level cache.
Change History (2)
comment:1 by , 18 years ago
| Milestone: | → BASE 2.0 |
|---|---|
| Status: | new → assigned |
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [2567]) Fixes #259: A job's progress doesn't get upadated when a job is executing in another virutal machine
The problem wasn't a virtual machine problem, but the progress wasn't saved to the database if the client supplied their own ProgressReporter object. This is the case for all test programs.