Launchpad itself

Repeated Chromium upload failures

Asked by Rob Savoury

Hello, today I am once again having problems with uploading Chromium. No error at all is given by dput, here is the terminal output:

D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-122.0.6261.94-0ubuntu0.18.04.1sav0_result/chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-122.0.6261.94-0ubuntu0.18.04.1sav0_result/chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_122.0.6261.94.orig.tar.xz: 3337929k/3337930k

This exact output has happened three times now this afternoon. As can be seen the upload fails to complete at the very end of the process which takes 50-60 minutes each time. Is there any known issue at present with large uploads to Launchpad?

In November 2023 after the major migration of the PPA service there were issues with large uploads [*] that were later fixed. This is the first time since then that I have had a repeated issue with uploading Chromium. Any help would be appreciated. Thank you.

[*] https://answers.launchpad.net/launchpad/+question/708481

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Clinton Fung
Solved:
Last query:
Last reply:
Revision history for this message
Rob Savoury (savoury1) said : 		#1

Fourth attempt at uploading this morning failed in exactly the same manner. No error, simply drops back to the terminal prompt after showing 3337929k/3337930k uploaded. Looking forward to a response about this issue as it is preventing me from getting the latest Chromium version built on Launchpad.

Revision history for this message
Guruprasad (lgp171188) said : 		#2

Hi Rob,

> Is there any known issue at present with large uploads to Launchpad?

We are investigating this and will get back to you as soon as possible. If you have the timestamps of when these failures happened, can you share those with us? If not, can you retry and share the timestamps if and when the failure happens?

Alternatively, can you also try uploading from a different internet connection, if possible and also try uploading using sftp instead of anonymous ftp? Using sftp gives additional identifying information in the logs for your sessions and helps us investigate.

Revision history for this message
Rob Savoury (savoury1) said : 		#3

Hi, thanks for the response and for looking into this issue. So today I attempted the upload again using sftp and it was successful. Not sure if anything was changed/fixed on the Launchpad backend? Or whether using sftp was the deciding factor.

In any case, here's the dput output wrapped with "date -uIns" commands to show the timestamps:

2024-03-01T18:11:49,744537633+00:00
D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-122.0.6261.94-0ubuntu0.18.04.1sav0_result/chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-122.0.6261.94-0ubuntu0.18.04.1sav0_result/chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via sftp to ppa.launchpad.net):
  Uploading chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_122.0.6261.94.orig.tar.xz: done.
  Uploading chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0.debian.tar.xz: done.
  Uploading chromium-browser_122.0.6261.94-0ubuntu0.18.04.1sav0_source.changes: done.
Successfully uploaded packages.
2024-03-01T23:34:42,474138653+00:00

As can be seen the upload took about 5 hours 23 minutes using sftp rather than the usual less than one hour with regular ftp. That slowdown of over five-fold is why I don't usually use sftp for uploading to Launchpad.

So I'm not sure if I should mark this as solved or not, given I don't know if anything was changed/fixed at the Launchpad side? For now I'll just submit this as more information.

Revision history for this message
Best Clinton Fung (clinton-fung) said : 		#4

In our internal discussion, we agreed to ask you to take these additional steps in order to get more information. We were unable to locate the cause of your problems previously, so we needed that extra info. Therefore, we weren't yet able to do anything on Launchpad's side to attempt to remediate

We think that this might be due to a timeout for a large upload.

I would propose closing this for now and opening something new if it happens again. In that case we would specifically want timestamps (relative to UTC) that would allow us to narrow down the logs, please.

Revision history for this message
Rob Savoury (savoury1) said : 		#5

OK, thanks for the response. Next time I do an upload of a new Chromium version I will once again try regular ftp first off. Plus, I will make sure to do the timestamps at the beginning and end of the dput invocation, as per the output for the successful upload via sftp that I posted above. Closing this as solved for now.

Revision history for this message
Rob Savoury (savoury1) said : 		#6

Thanks Clinton Fung, that solved my question.