grahamc/hydra - Change I7UELKBVDQOL47ZCBLDOLP3KUEFDNCWUPL4K4IG6FDRVVHOBWQ4QC

hydra-queue-runner: Don't unlock builds we just started

This happens if the previous iteration took more than 60 seconds. Then the queue runner may think that builds failed to start properly and unlock them, e.g.

build 5264936 pid 19248 died, unlocking build 5264951 pid 19248 died, unlocking build 5257073 pid 19248 died, unlocking …

Created by Eelco Dolstra on June 7, 2013

I7UELKBVDQOL47ZCBLDOLP3KUEFDNCWUPL4K4IG6FDRVVHOBWQ4QC

Dependencies

In channels

main

upstream

Change contents

Insertion in src/script/hydra-queue-runner at line 17 [5.7823]
[3.46]
[4.0]
```
my $lastTime;
```

Replacement in src/script/hydra-queue-runner at line 31 [5.7823]

B:BD[6.116] → [6.116:320]

B:BD[6.320] → [7.0:63]

∅:D[7.63] → [6.384:489]

B:BD[6.384] → [6.384:489]

B:BD[6.489] → [2.6837:6890]

                # Work around sqlite locking timeouts: if the child
                # barfed because of a locked DB before updating the
                # `locker' field, then `locker' is still set to $$.
                # So if after a minute it hasn't been updated,
                # unlock the build.  !!! need a better fix for those
                # locking timeouts.
                if ($build->starttime + 60 < time) {

[6.116]

[6.558]

                if (!defined $lastTime || $build->starttime < $lastTime - 300) {

Insertion in src/script/hydra-queue-runner at line 189 [5.7823]
[8.1644]
[9.886]
```
        $lastTime = time();
```

hydra-queue-runner: Don't unlock builds we just started

Dependencies

In channels

Change contents

Insertion in src/script/hydra-queue-runner at line 17 [5.7823]

Replacement in src/script/hydra-queue-runner at line 31 [5.7823]

Insertion in src/script/hydra-queue-runner at line 189 [5.7823]