Re: gokey mips build killed after too short timeout
On Mon, Jul 15, 2019 at 12:36:39 +0200, Benjamin Drung wrote: > Upstream ask in this bug report if the buildd run on real hardware of > virtualized. The builds run directly on the hardware, don't they? > https://db.debian.org/machines.cgi?host=mipsel-aql-01 doesn't say > anything about virtualization. > The mips* buildds are bare metal, yes. Cheers, Julien
Re: gokey mips build killed after too short timeout
Am Montag, den 15.07.2019, 12:29 +0200 schrieb Benjamin Drung: > Am Montag, den 15.07.2019, 12:00 +0200 schrieb Julien Cristau: > > On Mon, Jul 15, 2019 at 11:47:09 +0200, Benjamin Drung wrote: > > > > > Am Montag, den 15.07.2019, 11:42 +0200 schrieb Julien Cristau: > > > > On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > > > > > > > > > Hi, > > > > > > > > > > The gokey package has a test suite that takes very long to > > > > > execute > > > > > on > > > > > slow architectures. I had to set the golang test timeout to > > > > > six > > > > > hours, > > > > > because the gokey tests takes 11408.183 s (= 190 min) on > > > > > minkus.debian.org (mips porter box) [1]. > > > > > > > > > > The gokey 0.1.0-1 build on mipsel was killed after 150 > > > > > minutes > > > > > of > > > > > "inactivity". [2] Can you trigger the build again and > > > > > increase > > > > > the > > > > > kill-timeout? > > > > > > > > > That doesn't seem appropriate, IMO. That test should be made > > > > faster > > > > or > > > > disabled. > > > > > > All tests take 72 seconds in total on amd64. My guess it that it > > > somehow connected to entropy. > > > > > The host has a decent amount of entropy, so I doubt it: > > https://munin.debian.org/debian.org/mipsel-aql-01.debian.org/entropy.html > > I collected all execution times and reported it upstream, because > only > mips takes way longer than all other architectures (even mips64el is > around 5 times slower than armel): > > https://github.com/cloudflare/gokey/issues/28 > > I made a mistake in the initial mail: *mipsel* failed with the > timeout, > not *mips*. Upstream ask in this bug report if the buildd run on real hardware of virtualized. The builds run directly on the hardware, don't they? https://db.debian.org/machines.cgi?host=mipsel-aql-01 doesn't say anything about virtualization. -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
Re: gokey mips build killed after too short timeout
Am Montag, den 15.07.2019, 12:00 +0200 schrieb Julien Cristau: > On Mon, Jul 15, 2019 at 11:47:09 +0200, Benjamin Drung wrote: > > > Am Montag, den 15.07.2019, 11:42 +0200 schrieb Julien Cristau: > > > On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > > > > > > > Hi, > > > > > > > > The gokey package has a test suite that takes very long to > > > > execute > > > > on > > > > slow architectures. I had to set the golang test timeout to six > > > > hours, > > > > because the gokey tests takes 11408.183 s (= 190 min) on > > > > minkus.debian.org (mips porter box) [1]. > > > > > > > > The gokey 0.1.0-1 build on mipsel was killed after 150 minutes > > > > of > > > > "inactivity". [2] Can you trigger the build again and increase > > > > the > > > > kill-timeout? > > > > > > > That doesn't seem appropriate, IMO. That test should be made > > > faster > > > or > > > disabled. > > > > All tests take 72 seconds in total on amd64. My guess it that it > > somehow connected to entropy. > > > The host has a decent amount of entropy, so I doubt it: > https://munin.debian.org/debian.org/mipsel-aql-01.debian.org/entropy.html I collected all execution times and reported it upstream, because only mips takes way longer than all other architectures (even mips64el is around 5 times slower than armel): https://github.com/cloudflare/gokey/issues/28 I made a mistake in the initial mail: *mipsel* failed with the timeout, not *mips*. -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
Re: gokey mips build killed after too short timeout
Am Montag, den 15.07.2019, 12:00 +0200 schrieb Julien Cristau: > On Mon, Jul 15, 2019 at 11:47:09 +0200, Benjamin Drung wrote: > > > Am Montag, den 15.07.2019, 11:42 +0200 schrieb Julien Cristau: > > > On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > > > > > > > Hi, > > > > > > > > The gokey package has a test suite that takes very long to > > > > execute > > > > on > > > > slow architectures. I had to set the golang test timeout to six > > > > hours, > > > > because the gokey tests takes 11408.183 s (= 190 min) on > > > > minkus.debian.org (mips porter box) [1]. > > > > > > > > The gokey 0.1.0-1 build on mipsel was killed after 150 minutes > > > > of > > > > "inactivity". [2] Can you trigger the build again and increase > > > > the > > > > kill-timeout? > > > > > > > That doesn't seem appropriate, IMO. That test should be made > > > faster > > > or > > > disabled. > > > > All tests take 72 seconds in total on amd64. My guess it that it > > somehow connected to entropy. > > > The host has a decent amount of entropy, so I doubt it: > https://munin.debian.org/debian.org/mipsel-aql-01.debian.org/entropy.html Then I do not have a clue why it takes soo much longer on mips than on amd64. -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
Re: gokey mips build killed after too short timeout
Am Montag, den 15.07.2019, 11:42 +0200 schrieb Julien Cristau: > On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > > > Hi, > > > > The gokey package has a test suite that takes very long to execute > > on > > slow architectures. I had to set the golang test timeout to six > > hours, > > because the gokey tests takes 11408.183 s (= 190 min) on > > minkus.debian.org (mips porter box) [1]. > > > > The gokey 0.1.0-1 build on mipsel was killed after 150 minutes of > > "inactivity". [2] Can you trigger the build again and increase the > > kill-timeout? > > > That doesn't seem appropriate, IMO. That test should be made faster > or > disabled. All tests take 72 seconds in total on amd64. My guess it that it somehow connected to entropy. -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
Re: gokey mips build killed after too short timeout
On Mon, Jul 15, 2019 at 11:47:09 +0200, Benjamin Drung wrote: > Am Montag, den 15.07.2019, 11:42 +0200 schrieb Julien Cristau: > > On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > > > > > Hi, > > > > > > The gokey package has a test suite that takes very long to execute > > > on > > > slow architectures. I had to set the golang test timeout to six > > > hours, > > > because the gokey tests takes 11408.183 s (= 190 min) on > > > minkus.debian.org (mips porter box) [1]. > > > > > > The gokey 0.1.0-1 build on mipsel was killed after 150 minutes of > > > "inactivity". [2] Can you trigger the build again and increase the > > > kill-timeout? > > > > > That doesn't seem appropriate, IMO. That test should be made faster > > or > > disabled. > > All tests take 72 seconds in total on amd64. My guess it that it > somehow connected to entropy. > The host has a decent amount of entropy, so I doubt it: https://munin.debian.org/debian.org/mipsel-aql-01.debian.org/entropy.html Cheers, Julien
Re: gokey mips build killed after too short timeout
On Mon, Jul 15, 2019 at 11:18:11 +0200, Benjamin Drung wrote: > Hi, > > The gokey package has a test suite that takes very long to execute on > slow architectures. I had to set the golang test timeout to six hours, > because the gokey tests takes 11408.183 s (= 190 min) on > minkus.debian.org (mips porter box) [1]. > > The gokey 0.1.0-1 build on mipsel was killed after 150 minutes of > "inactivity". [2] Can you trigger the build again and increase the > kill-timeout? > That doesn't seem appropriate, IMO. That test should be made faster or disabled. Cheers, Julien
gokey mips build killed after too short timeout
Hi, The gokey package has a test suite that takes very long to execute on slow architectures. I had to set the golang test timeout to six hours, because the gokey tests takes 11408.183 s (= 190 min) on minkus.debian.org (mips porter box) [1]. The gokey 0.1.0-1 build on mipsel was killed after 150 minutes of "inactivity". [2] Can you trigger the build again and increase the kill-timeout? [1] https://salsa.debian.org/go-team/packages/gokey/commit/e8b08364912589ce80ea8274cae7b3384097a4c4 [2] https://buildd.debian.org/status/fetch.php?pkg=gokey&arch=mipsel&ver=0.1.0-1&stamp=1562699632&raw=0 -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
