If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Sisyphus - should use unittest account on unittest machines

RESOLVED FIXED

Status

Testing
Sisyphus
RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: bc, Assigned: bc)

Tracking

Trunk
x86
All
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
Currently, Sisyphus has anonymous pserver set in set-build-env.sh for checking out from cvs-mirror. This causes the unittest machines to lag the actual checkins by 15+ minutes. set-build-env.sh should be able to detect whether it has a unittest private key and use that when running on the unittest boxes.
Flags: in-testsuite-
Flags: in-litmus-
(Assignee)

Comment 1

10 years ago
Created attachment 315258 [details] [diff] [review]
patch

If CVSROOT already set use that, else if "unittest" account exists in id_dsa.pub, then use unittest else use anonymous.
Attachment #315258 - Flags: review?(rcampbell)
Comment on attachment 315258 [details] [diff] [review]
patch

This makes me a little uneasy since you could see a test failure due to cvs update lag, but since they're automated, they would clear on the next update.
Attachment #315258 - Flags: review?(rcampbell) → review+
(Assignee)

Comment 3

10 years ago
Actually, the current setup _always_ uses the anon pserver. This just allows it to use unittest if it is available.

/cvsroot/mozilla/testing/sisyphus/bin/set-build-env.sh,v  <--  set-build-env.sh
new revision: 1.7; previous revision: 1.6
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Mass move of Sisyphus bugs to Testing : Sisyphus. Filter on SisyphusMassMove to ignore.
Component: Testing → Sisyphus
Flags: in-litmus-
Product: Core → Testing
QA Contact: testing → sisyphus
You need to log in before you can comment on or make changes to this bug.