1488331 - aarch64 CI builds aren't running --ct-verif

Status: NEW

(NSS :: Test, defect, P5)

Description

[Martin Thomson [:mt:]]

It took me a while to understand this, but the order of arguments to merge is not right here:

https://searchfox.org/nss/rev/9c9f834050b7daee2c1ea964ebb6198851f4fcd6/automation/taskcluster/graph/src/extend.js#733-750

Basically, anything that was in the `base` was overriding the config here.  This meant that these builds were running something that is more or less a duplicate of other builds.

For this run here: https://treeherder.mozilla.org/#/jobs?repo=nss&revision=229a3a57f42a2ea78bf83c88c7df52bf8b1488b9&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=running&filter-resultStatus=pending&filter-resultStatus=runnable&filter-resultStatus=retry&filter-resultStatus=success

This is supposedly the special build:
https://tools.taskcluster.net/groups/ghEgQjSORRSnT0d8Z8g4-w/tasks/ghEgQjSORRSnT0d8Z8g4-w/details

Which is basically the same as the basic build:
https://tools.taskcluster.net/groups/pWqs4YpYTE2yCv63eo90kw/tasks/pWqs4YpYTE2yCv63eo90kw/details

Also the name of the build is lame and needs fixing.

Comment 1

[Martin Thomson [:mt:]]

Correction: this is only for aarch64.  It appears that other platforms don't set a command before invoking the buggy function.

Comment 2

[Martin Thomson [:mt:]]

Current plan is to disable these builds.  Until bug 1488325 is fixed and we can change the docker images that are used to run these builds, we can't get valgrind to fix a build issue on the machines.