This time

I almost got to use one of my Vagabonds last night... We had a Cyclone in Chaos Central. Unfortunately by the time I had fleeted up, he had exited the system. Ah well, can't win them all.

For the next test I am going to try to re-prove that only the latest submit on a planet gets the bug. So I setup a 20h job and a 40h job. 4 processors setup All materials there. This time I start both jobs one after the other. First the 20 h job. Hit submit. Then the 40h job. Started at 3:53 and 3:55 respectively. No further submits happen on character. We'll see what happens. I also intend to only log in after 12:00 eve time and hopefully I will cause the system to be loaded at that time. Here's what I'm hoping the results will be:

20h job on track but with 1 cycle gone poof (the destroyed materials bug)
40h job finished completely.

Lets see what we get...

12:05... extended downtime ... again ... time for a shower...

(incidentally all times I state are EVE times - in case that was not made clear).

Ok I did get the 40h finishing off at downtime - as expected and the 20h not finishing. Someone else caused the system to load so I was not able to get a positive result for that part of the test (the theory that the loss is related to the system loading...)

This at least confirms that the actual hour before downtime is irrelevant (I'm still setting it up withing the 15min before the hour though) and the bug shows up based on the most recent submit (no idea if it's for that planet or for the character though). Tomorrow's test will be to see if the submit for the extractors also causes the bug not to show up.