Project

General

Profile

Bug #8632

Upload job archive is restricted while another job is running

Added by Anton Vasilyev over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
12/15/2017
Due date:
12/18/2017
% Done:

100%

Estimated time:
Detected in build:
eb8dee3d0620b8cdf6b5a962049cdd98cd583392
Platform:
Published in build:

Description

I'm trying to upload job archive on instance with one running job and catch error message:
"There are jobs in progress right now, uploading may corrupt it results. Please wait until it will be finished."

Does it really necessary to restrict this kind of uploading?

History

#1

Updated by Evgeny Novikov over 1 year ago

  • Assignee changed from Evgeny Novikov to Vladimir Gratinskiy
  • Priority changed from Normal to Urgent
  • Target version set to 2.0

I also met this issue several times last days. I didn't remember exact reasons why this is so. Maybe this is because of uploading a job archive can take quite much time during which reports of solved jobs couldn't be uploaded. But everything changes from that time. Now even large job archives are uploaded very quickly while blocking requests likely doesn't result in failing job solutions.

#2

Updated by Vladimir Gratinskiy over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
  • Due date set to 12/18/2017

Fixed in "fix_8632" together with #8384 and #8626.

#3

Updated by Evgeny Novikov over 1 year ago

  • Target version changed from 2.0 to 1.0

As far as we postpone Klever version:0.3, let's include this issue there.

#4

Updated by Ilja Zakharov over 1 year ago

  • Status changed from Resolved to Verified
#5

Updated by Ilja Zakharov over 1 year ago

  • Status changed from Verified to Closed

Available since 93bb9af9.

Also available in: Atom PDF