Closed Bug 1773210 Opened 2 years ago Closed 2 years ago

Setup a branch for clang-trunk builds

Categories

(Developer Services :: Mercurial: hg.mozilla.org, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glandium, Assigned: sheehan)

References

(Blocks 1 open bug)

Details

In the context of setting up regular builds against clang-trunk (and in the future rustc-nightly as well), which would run the same set of builds and tests as mozilla-central, we want to set up a dedicated branch where the content of mozilla-central would be pushed to regularly to trigger clang-trunk builds. The branch would be sheriffed.

Ideally, this would be an integration/something branch (e.g. integration/toolchains), but https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning suggests we don't do that anymore (funnily enough, the page it redirects to sends you back where you came from if you read the instructions and find that you don't want a disposable branch).

I had a sort of epiphany under the shower. Aryx, would it make sense to set this up in a way that sheriffs could push clang-trunk builds/tests to try like they do for e.g. central-as-release, and sheriff that? Because come to think of it, that would make it easier for developers to do such clang-trunk trys as well.

Flags: needinfo?(aryx.bugmail)
  1. How often should the builds and tests run?
  2. Regarding tests, are the failures obviously from the clang changes?
Flags: needinfo?(aryx.bugmail)

(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #2)

  1. How often should the builds and tests run?

At least once a day.

  1. Regarding tests, are the failures obviously from the clang changes?

If we get errors that don't already happen on autoland/central, usually they are from clang changes. They can be filed in the toolchains component.

Flags: needinfo?(aryx.bugmail)

Glandium and I discussed this. Let's start with 2 runs per week on a project branch.

Flags: needinfo?(aryx.bugmail)

Let's get the ball rolling. Connor, can you create the project branch?

Flags: needinfo?(sheehan)

Sure, I'll do that now.

Assignee: nobody → sheehan
Flags: needinfo?(sheehan)

Okay this is set up as https://hg.mozilla.org/projects/clang-trunk/

Repo name can be changed if need be, and there are no hooks enabled on the repo right now. Let me know when this is added to TH so I can add the config for links to appear in the terminal on push.

I'm going to set up clonebundles and such as well.

Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/ee06341e59d7
bundles: add projects/clang-trunk to bundle repo list
https://hg.mozilla.org/hgcustom/version-control-tools/rev/93e7212e6e47
mozautomation: add clang-trunk to repo lists

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

(In reply to Connor Sheehan [:sheehan] from comment #7)

Okay this is set up as https://hg.mozilla.org/projects/clang-trunk/

Repo name can be changed if need be

Can you rename to projects/toolchains?

I'm going to set up clonebundles and such as well.

FWIW, no need for branch specific bundles, you can point to central, the repo will be identical.

Flags: needinfo?(sheehan)

https://hg.mozilla.org/projects/toolchains/

Good call, I'll set the toolchains to copy from central tomorrow.

Flags: needinfo?(sheehan)
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/2f90f1ee9ea7
bundles: change `projects/clang-trunk` to `projects/toolchains` and copy bundles from central
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/5ac9bdbba466
mozautomation: change `clang-trunk` to `toolchains`

I supposed it'll take some more time before curl -sL https://hg.mozilla.org/projects/toolchains?cmd=clonebundles stops returning projects/clang-trunk...
(Note: the copyfrom thing could just make the server return the actual same clonebundles manifest rather than duplicating the bundles on the S3/GCS side)

(In reply to Mike Hommey [:glandium] from comment #13)

I supposed it'll take some more time before curl -sL https://hg.mozilla.org/projects/toolchains?cmd=clonebundles stops returning projects/clang-trunk...
(Note: the copyfrom thing could just make the server return the actual same clonebundles manifest rather than duplicating the bundles on the S3/GCS side)

Sorry about that - should be resolved on the next bundles generation.

Blocks: 1786761

Connor, can the repo be changed to SCM level 2 per discussion in https://phabricator.services.mozilla.com/D156141?

Flags: needinfo?(sheehan)
Flags: needinfo?(sheehan)
You need to log in before you can comment on or make changes to this bug.