On Thu, Jul 06, 2017 at 11:58:13AM -0700, Steve Langasek wrote: > On Thu, Jul 06, 2017 at 07:26:19AM +0200, Petter Reinholdtsen wrote: > > [Steve Langasek] > > > FWIW this does fix the problem with the test talking to the wrong server, > > > but the test still fails as shown at > > > <https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/sitesummary/20170706_010816_63bee@/log.gz>. > > > Hm, look like a race condition: > > > autopkgtest [01:08:03]: test test-server-client: [----------------------- > > /var/lib/sitesummary > > /var/lib/sitesummary/tmpstorage > > /var/lib/sitesummary/tmpstorage/127.0.0.1-2017-07-06T01:08:03-2349-sitesummary > > /var/lib/sitesummary/tmpstorage/127.0.0.1-2017-07-06T01:08:03-2349-sitesummary.tar.gz > > /var/lib/sitesummary/www > > /var/lib/sitesummary/www/index.html > > /var/lib/sitesummary/entries > > error: did not find entry > > info: terminating script > > autopkgtest [01:08:04]: test test-server-client: -----------------------] > > > > It look like the server is still busy unpacking the submitted entry, and > > have not yet had time to move the relevant files under entries/. > > > Anyone got any idea how we can best avoid the race? 'sleep 10' seem > > like such a crude solution... > > Ah. Seems to me like either a sleep or a poll are your only options. I > don't know how much processing sitesummary has to do, but maybe a one minute > timeout on a poll would be reasonable? There's not much to do, it's rather seconds than a minute; the overview page shows the test failing only randomly, times differ as well: https://ci.debian.net/packages/s/sitesummary/unstable/amd64/ Wolfgang
Attachment:
signature.asc
Description: PGP signature