Closed MichaelRoeder closed 7 years ago
The problem seems to occur at runtime as well.
It needs to be clearified whether it is a problem of the queue status printing methods (i.e., the order does not change but it is shown in a wrong way that might lead to the impression that the order changes) or whether the order is really changing.
The sorting had to be removed since it was not working properly (d3fb5465182a3c7145a6462f81dc86e1a3d1b815). That means that the queue is now working in the correct order, but when asked for the status, the printed order might be different.
Either the experiment queue itself or its representation in the GUI (http://master.project-hobbit.eu/#/benchmarks/validate) change the order of experiments after the platform has been restarted.
It should keep the order of experiments following the FIFO principle. This could be checked by the experiment IDs that should occur in an ascending order.