'No Experiment Runs registered'
Hi team,
I think this is an important issue that we are currently facing off. In this past weeks I've seen a lot of experiments with the following conditions:
- No experiments runs registered.
- Execution times are 0 whenever the job is finished.
At the moment of writing this 8:32am 22nd of December, there are 4 out of the total of 18 active experiments are facing this issue.
| expid | as version | link |
|---|---|---|
| a5bj | 3.14.0b0 | See |
| a5i0 | 3.14.0 | See |
| a5hc | 3.14.0b0 | See |
| a5hl | 3.14.0b0 | See |
The problem resides that the job_data_<expid>.db tables (experiment_runs and job_data) are empty. History's module of Autosubmit is who should be creating this tables so I think there's a bug but still haven't located it.
My guess is the same as what I've planned in this discussion with Eric. This history module of Autosubmit responsible of creating new runs recently has been updated adding new fields (see Issue #847: Database runid update) and since then, new experiments created are vulnerable to this bug. Could be the case(?)