616008 - nanojit tinderbox cannot 'hg update'

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Nicholas Nethercote [inactive]]

The nanojit tinderbox (added in bug 506404) has been totally red the last couple of commits.  It appears that 'hg update' is failing on all platforms.  Here's a sample log:

http://tinderbox.mozilla.org/showlog.cgi?log=Nanojit/1291242568.1291242587.16845.gz

Comment 1

[[e-mail] (:bhearsum)]

Caused by some recent changes to shared code...Catlee and I are figuring out how to fix this.

Comment 2

[[e-mail] (:bhearsum)]

Attachment: use different property for ScriptFactory revision

Untested, but should work. I'll try it in staging today.

Comment 3

[[e-mail] (:bhearsum)]

Attachment: update release scripts that depend on revision

I think this everything that needs updating (besides the docs) to cope.

Comment 4

[[e-mail] (:bhearsum)]

Comment on attachment 494697 [details] [diff] [review]
use different property for ScriptFactory revision

I somehow managed to land the buildbotcustom patch when I was doing other landings today :(. The good news is that it _does_ work. Unfortunately, it's incomplete, I'm going to need a follow-up.

Comment 5

[[e-mail] (:bhearsum)]

Attachment: remove doStepIf

Since WithProperties defaults to 'default', we can safely run this step all the time.

Comment 6

[[e-mail] (:bhearsum)]

Attachment: typo fix

I tested this patch in staging by starting a staging run with release_sanity.py. Both the "update scripts" step and tag-release.py updated to the correct revision.

L10n worked similarly, but I executed it through "Force Build".

Comment 7

[[e-mail] (:bhearsum)]

Comment on attachment 495081 [details] [diff] [review]
typo fix

changeset:   1819:74254d531776

Comment 8

[[e-mail] (:bhearsum)]

Comment on attachment 495066 [details] [diff] [review]
remove doStepIf

Landed in changeset:   1247:0ef69eb28bd1, merged to the production-0.8 branch in 1250:30537b778f04

Comment 9

[[e-mail] (:bhearsum)]

Should be all fixed now!

Comment 10

[Nicholas Nethercote [inactive]]

(In reply to comment #9)
> Should be all fixed now!

I can confirm that it is fixed, thank you.