--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CALNjmMp7-s9AhKqxiMB%2ByoLJZH%2BrGkET9CfsE28%2B%3DVpkOHDrcQ%40mail.gmail.com.
1 | 2019-06-10 18:22:50.497974 UTC | ||
2 | 2019-05-29 20:13:32.773355 UTC | ||
3 | 2019-05-29 20:13:32.773355 UTC | ||
4 | 2019-05-29 20:03:13.944131 UTC | ||
5 | 2019-05-29 19:59:08.249830 UTC | ||
6 | 2019-05-21 00:02:11.416646 UTC | ||
7 | 2019-05-20 23:57:27.685605 UTC | ||
8 | 2019-05-20 19:00:55.737826 UTC | ||
9 | 2019-05-17 12:57:32.186618 UTC | ||
10 | 2019-05-17 12:53:01.921649 UTC | ||
11 | 2019-05-10 00:54:47.716807 UTC | ||
12 | 2019-05-07 07:31:58.044902 UTC | ||
13 | 2019-05-07 06:53:59.627882 UTC | ||
14 | 2019-05-03 22:45:37.672018 UTC | ||
15 | 2019-04-25 22:02:35.649821 UTC | ||
16 | 2019-04-16 22:28:23.332535 UTC | ||
17 | 2019-04-08 21:31:29.647127 UTC | ||
18 | 2019-04-08 21:28:08.048893 UTC | ||
19 | 2019-04-02 10:48:26.426473 UTC | ||
20 | 2019-04-02 03:14:26.484550 UTC | ||
21 | 2019-04-02 03:04:35.950857 UTC | ||
22 | 2019-04-02 02:58:24.057070 UTC | ||
23 | 2019-03-26 18:47:56.158290 UTC | ||
24 | 2019-03-20 17:42:17.897407 UTC | ||
25 | 2019-03-19 19:07:31.649379 UTC | ||
26 | 2019-03-19 19:00:57.671292 UTC | ||
27 | 2019-03-14 05:35:05.859369 UTC | ||
28 | 2019-03-14 05:24:51.512822 UTC | ||
29 | 2019-03-14 05:22:11.353553 UTC |
If you still concern this builder removal, how do you think removing bots for 32bit linux test only?
OK.Currently, my decision is keeping 32bit linux CI/CQ builder only do building.
On Wed, Jun 12, 2019 at 2:40 AM Reid Kleckner <> wrote:
On Tue, Jun 11, 2019 at 6:22 AM 'Takuto Ikuta' via Chromium-dev <> wrote:If you still concern this builder removal, how do you think removing bots for 32bit linux test only?I think doing compile-only testing of 32-bit Linux is a good idea, assuming that compilation is relatively cheap compared to testing.
--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/a32a0197-80d6-4cb6-9e78-b42a0caef736%40chromium.org.
Sorry for the slow reply here, I've been on vacation.From what I understand, while we no longer ship 32-bit linux, we still want to support building and running tests on it, for several reasons:- Clusterfuzz wants to use 32-bit linux because fuzzers find more issues when pointers are smaller.- 32-bit ARM is still very common, and 32-bit linux x86 finds issues that 32-bit ARM finds, like Jakob says. You replied to this point with an analysis that failures on that bot aren't 32-bit specific, but that doesn't answer that it's still useful for development.There's an old, internal thread ("Deprecating x86 (32-bit) Linux Support") on an internal list from 2015 where the conclusion was to keep bots for this config around. (+jam since he was active on that thread.)I'm all in favor of having fewer configurations and if we could completely stop supporting 32-bit Linux builds, I think that'd be awesome. But as-is, we still support them, but have fewer public bots that check that things work, so we now learn about breakages from Clusterfuzz bugs, which seems worse than before.So I think you should either try to convince the clusterfuzz folks to stop using 32-bit binaries and make sure v8 is happen without a 32-bit x86 build as well, or we should keep bots for this config around.