Closed Bug 1719608 Opened 3 years ago Closed 3 years ago

Make robustcheckout compatible with up to Mercurial 5.8

Categories

(Developer Services :: Mercurial: robustcheckout, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(3 files)

No description provided.
Blocks: 1719622

Can this land in a fashion which prevents older pushes and the ones on other trees from using workers which have been set up with Mercurial 5.8 (which broke tasks from other Try pushes earlier today)?

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

(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #4)

Can this land in a fashion which prevents older pushes and the ones on other trees from using workers which have been set up with Mercurial 5.8 (which broke tasks from other Try pushes earlier today)?

Do you have links? Because that shouldn't be happening.

Flags: needinfo?(aryx.bugmail)

See these pushes (top one regenerated toolchains, packages, docker images etc.).

Flags: needinfo?(aryx.bugmail)

Oh! caches... There are two ways around this: switching to a new cache, or change robustcheckout to clone from scratch when such errors happen. Considering things like bug #1539681, I'm tempted to say we should go with the latter. Connor, what do you think?

Flags: needinfo?(sheehan)

Mmmm that said, changing robustcheckout wouldn't solve the problem for try pushes of older code without the change...

Flags: needinfo?(sheehan)
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/a14b33a964c3
Make robustcheckout compatible with up to Mercurial 5.8. r=sheehan
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: