Closed
Bug 1346063
Opened 7 years ago
Closed 7 years ago
Re-checkout test262/local when updating test262
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: shu, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
3.28 KB,
patch
|
anba
:
review+
|
Details | Diff | Splinter Review |
We're going to work with Bocoup to improve the keeping local + upstreaming of test262 tests. Until then, I'm sticking things into test262/local. The update script recreates the entire directory from scratch. Make it re-checkout local/ after recreating.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Updated•7 years ago
|
Attachment #8845694 -
Flags: review?(andrebargull)
Comment 2•7 years ago
|
||
I haven't actually merged the patch locally to test this, but it seems like this approach only works when git is used for the local mozilla tree. I think you need to move the "local" directory to a temp-location and move it back after the test262 update. Or alternatively detect when mercurial is used to work with the mozilla tree.
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to André Bargull from comment #2) > I haven't actually merged the patch locally to test this, but it seems like > this approach only works when git is used for the local mozilla tree. I > think you need to move the "local" directory to a temp-location and move it > back after the test262 update. Or alternatively detect when mercurial is > used to work with the mozilla tree. Oh derp, that probably the majority of people do not use git for m-c escaped me.
Reporter | ||
Comment 4•7 years ago
|
||
Also snuck in a SAB feature test skip-if in there, was too lazy to open a new bug.
Reporter | ||
Updated•7 years ago
|
Attachment #8845694 -
Attachment is obsolete: true
Attachment #8845694 -
Flags: review?(andrebargull)
Reporter | ||
Updated•7 years ago
|
Attachment #8846128 -
Flags: review?(andrebargull)
Comment 5•7 years ago
|
||
Comment on attachment 8846128 [details] [diff] [review] Don't remove test262/local when updating test262. Review of attachment 8846128 [details] [diff] [review]: ----------------------------------------------------------------- ::: js/src/tests/test262-update.py @@ +388,5 @@ > # Copy the test files. > process_test262(inDir, outDir, strictTests) > > + # Move test262/local back. > + shutil.move(os.path.join(inDir, "local"), outDir) If |os.path.isdir(localTestsOutDir)| is false, "local" doesn't get moved to |inDir|. Does shutil.move ignore non-existent files or will this line throw an exception in that case?
Attachment #8846128 -
Flags: review?(andrebargull) → review+
Reporter | ||
Comment 6•7 years ago
|
||
(In reply to André Bargull from comment #5) > Comment on attachment 8846128 [details] [diff] [review] > Don't remove test262/local when updating test262. > > Review of attachment 8846128 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: js/src/tests/test262-update.py > @@ +388,5 @@ > > # Copy the test files. > > process_test262(inDir, outDir, strictTests) > > > > + # Move test262/local back. > > + shutil.move(os.path.join(inDir, "local"), outDir) > > If |os.path.isdir(localTestsOutDir)| is false, "local" doesn't get moved to > |inDir|. Does shutil.move ignore non-existent files or will this line throw > an exception in that case? Good catch, I'll make it only move back if the script moved it in the first place.
Pushed by shu@rfrn.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/8043a5044362 Don't remove test262/local when updating test262. (r=anba)
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8043a5044362
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•