1529963 - Intermittent failure for custom-v8

Status: RESOLVED DUPLICATE of bug 1519816

(Firefox Build System :: Task Configuration, task)

Description

[Barret Rennie [:barret] (they/them)]

Attachment: custom-v8.log

I am intermittently getting failures for the custom-v8, seemingly because of network failure:

[task 2019-02-22T17:52:33.671Z] W: Failed to fetch http://snapshot.debian.org/archive/debian/20170830T000511Z/dists/stretch/InRelease  Could not connect to snapshot.debian.org:80 (2001:1af8:4020:b030:deb::185). - connect (101: Network is unreachable) [IP: 2001:1af8:4020:b030:deb::185 80]
[task 2019-02-22T17:52:33.671Z] W: Failed to fetch http://snapshot.debian.org/archive/debian/20170830T000511Z/dists/stretch-updates/InRelease  Unable to connect to snapshot.debian.org:http: [IP: 2001:1af8:4020:b030:deb::185 80]
[task 2019-02-22T17:52:33.671Z] W: Failed to fetch http://snapshot.debian.org/archive/debian/20170830T000511Z/dists/stretch-backports/InRelease  Unable to connect to snapshot.debian.org:http: [IP: 2001:1af8:4020:b030:deb::185 80]
[task 2019-02-22T17:52:33.671Z] W: Failed to fetch http://snapshot.debian.org/archive/debian-security/20170830T000511Z/dists/stretch/updates/InRelease  Unable to connect to snapshot.debian.org:http: [IP: 2001:1af8:4020:b030:deb::185

Also I'm not sure that this is the right component, but treeherder did not give me the option to file a bug automatically as the failure summary contains:

No Bug Suggestions Available.
Unsuccessful Execution Steps

    Unnamed step : unknown.View log

Comment 1

[Andrew Halberstadt [:ahal]]

Looks like a problem in the docker image, moving over to Task Configuration. I also cc'ed a few people who might know a bit more.

Comment 2

[Greg Mierzwinski [:sparky]]

This may be related to the change made in bug 1519816. That bug moved all the build dependency installations into the docker image and the errors that occurred in the toolchain build were similar to this one.

Comment 3

[Mike Hommey [:glandium]]

You pushed a tree from 2 weeks ago, where bug 1519816 is not fixed, so yeah, you hit bug 1519816.

Relatedly, did you run mach try fuzzy -q linux64 or mach try fuzzy --full -q linux64? If the former, toolchain jobs shouldn't have run (and a bug should be filed), and if the latter, you maybe shouldn't use --full.

Comment 4

[Barret Rennie [:barret] (they/them)]

I was indeed running ./mach try fuzzy -q linux64. I did not specify --full.

Comment 5

[Mike Hommey [:glandium]]

Filed bug 1530038