Project

General

Profile

action #21818

Two workers can work on the same job at a time

Added by dasantiago about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
2017-08-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

The web interface is showing wrong image for an assert screen:

https://openqa.suse.de/tests/1096055#step/shotwell_edit/20

If we look into the video, it looks like that the match was done correctly, however in the webinterface it shows the needle comparison against a wrong screen.

Please check the job above, for more info.


Related issues

Related to openQA Tests - action #20378: [tools]Too many 502 on openqaResolved2017-07-18

History

#1 Updated by coolo about 4 years ago

  • Subject changed from Web-interface is showing wrong image to Two workers can work on the same job at a time
  • Assignee set to EDiGiacinto
  • Priority changed from Normal to Urgent

2620:113:80c0:8080:10:160:0:243 - - 07/Aug/2017:15:33:50 +0200 "POST /api/v1/jobs/1096055/status HTTP/1.1" 200 52 "-" "Mojolicious (Perl)"
2620:113:80c0:8080:10:160:68:197 - - 07/Aug/2017:15:33:52 +0200 "POST /api/v1/jobs/1096055/status HTTP/1.1" 200 52 "-" "Mojolicious (Perl)"

The workaround for it (checking worker_id) was taken out as it caused other problems, but the underlying problem that a worker can have a job it shouldn't have, persists.

#2 Updated by EDiGiacinto about 4 years ago

yes, shouldn't exists, but for the record there will always be a timeframe when we send abort to a worker and we assign the same job to another one. In that time frame the old worker can still try to update the job

#3 Updated by EDiGiacinto about 4 years ago

#4 Updated by EDiGiacinto about 4 years ago

  • Status changed from New to In Progress

#5 Updated by EDiGiacinto about 4 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF