Closed
Bug 671813
Opened 13 years ago
Closed 13 years ago
integration-check tool fails its "sample packaging tests"
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: myk, Assigned: myk)
Details
Attachments
(1 file)
880 bytes,
text/plain
|
Details |
The integration-check tool fails its "sample packaging tests". Here's the terminal output: -------------------------------------------------------------------------------- $ ../addon-sdk/bin/integration-scripts/integration-check --url https://ftp.mozilla.org/pub/mozilla.org/labs/jetpack/addon-sdk-1.0.tar.gz Your Base path is =c:\Users\myk\foo\ gz file present in the URL File name is =addon-sdk-1.0.tar.gz Your local file path will be=c:\Users\myk\foo\addon-sdk-1.0.tar.gz Downloading...Please be patient! Download was successful. Folder Name= addon-sdk-1.0 Starting to Extract... Extraction Successful. Starting tests... Results are logged at:c:\Users\myk\foo\tests.log All tests were successful. Yay \o/ . Running a sample package test now... Now Running packaging tests... Sample tests were not executed correctly. Check the test-example log in jetpack diretory. Sample test results are logged at:c:\Users\myk\foo\test-example.log Ending program -------------------------------------------------------------------------------- I've attached the test-example.log file. I'm guessing this is because cfx behavior changed at some point, and integration-check was not updated to work with the change.
Assignee | ||
Comment 1•13 years ago
|
||
P1 at least until we know why the test is failing and what to do about it.
Priority: -- → P1
Target Milestone: --- → 1.1
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → myk
Priority: P1 → P2
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.1 → ---
Assignee | ||
Comment 3•13 years ago
|
||
This is no longer happening, although I don't know why.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•