Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage should be stopped immediately if a storage is already going on with the same name #1013

Closed
bruntib opened this issue Oct 9, 2017 · 0 comments

Comments

@bruntib
Copy link
Contributor

bruntib commented Oct 9, 2017

The mass storage has two phases: storing the files and storing the results. The latter one happens in a separate transaction. At the beginning of this transaction it is checked whether there is another transaction which stores the same run name. We get an error message for this but only after the storage of files. If a large .zip is uploaded then it takes some time. We should do the checking before the file storage.

@gyorb gyorb modified the milestones: release 6.0.2, release 6.1, release 6.2, 6.1.1 Oct 9, 2017
@bruntib bruntib self-assigned this Oct 17, 2017
bruntib added a commit to bruntib/codechecker that referenced this issue Oct 17, 2017
We shouldn't wait for file storage to notice that another storage with
the same name is already going.
Fixes Ericsson#1013
bruntib added a commit to bruntib/codechecker that referenced this issue Oct 17, 2017
We shouldn't wait for file storage to notice that another storage with
the same name is already going.
Fixes Ericsson#1013
bruntib added a commit to bruntib/codechecker that referenced this issue Oct 17, 2017
We shouldn't wait for file storage to notice that another storage with
the same name is already going.
Fixes Ericsson#1013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants