-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
Lost packages after publication #1376
Comments
Hi ! The Jenkins output looks ok to me... this is just one of the parallel runs ? some more questions: Does each run use a unique upload dir (tmp.U5FXf4EUJcvNTWu) ? |
@neolynx hi!
|
thanks for the explanations ! I think I found the race condition: async background operation was not implemented to do all database operation inside a synchronized block, so for example adding a directory to a repo would read the repo contents, and then run the background tasks. If 2 run at the same time, the could both read a emptry repo, and then in the background operation, on of them wins. since you are compiling aptly, could you try commit f16a68f from the branch fix/concurrent-api ? this should fix most race conditions (except maybe deleting the repo while adding files) |
fix has been merged to master... please test again ! |
Oh! Thanks! :-) |
@neolynx I built aptly from master and tested it. Everything works perfectly! |
thank you for finding and reproducing this ! |
Hi! After resolved #1276 I builded and installed
aptly
version1.5.0+207+g372ce3c4
And now some big packages (>900 Mb) are lost with concurent builds on Jenkins.
When uploading and publishing the package I get status 2, but the package is not in the repository.
For example, the package
testfile_4.4.5.7667
was lost.Please, help me understand, why this is happening?
In aptly access.log file:
In Jenkins console output:
The text was updated successfully, but these errors were encountered: