Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nov.12 release test_manifest.sh failed on 'Testing redundant manifest with matching file' test #91

Open
GoogleCodeExporter opened this issue Jun 2, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.Execute run_tests.py

What is the expected output? What do you see instead?

Executing test_manifest.sh...
Finished in 0.0 seconds
New session 'TestSession' was created successfully
Finished in 0.01 seconds
-- Testing simple case happy path
-- Testing manifest mismatch
-- Testing manifest conflict
-- Testing manifest checksum error
-- Testing redundant manifests with matching file
*** Text mismatch
Mismatch at line 0 (magic = '!')
expected: NOTICE: Using manifest file manifest-md5.txt
expected: NOTICE: Using manifest file 
manifest-6f0d05d79c11595917d4ebe31a18fbb1.md5
expected: Sending manifest-6f0d05d79c11595917d4ebe31a18fbb1.md5
expected: Checked in session id 3
expected: !Finished in .* seconds
actual  : NOTICE: Using manifest file 
manifest-6f0d05d79c11595917d4ebe31a18fbb1.md5
actual  : NOTICE: Using manifest file manifest-md5.txt
actual  : Sending manifest-6f0d05d79c11595917d4ebe31a18fbb1.md5
actual  : Checked in session id 3
actual  : Finished in 0.06 seconds
Import with redundant manifests gave unexpected message
*** Test case test_manifest.sh failed (/tmp/boar-test_manifest.sh.MMboPn)
*** Output in /tmp/boar-test_manifest.sh.MMboPn.log
Macrotests (local) failed


What platform are you using? (Windows XP, Windows 7, Linux, ...)
Linux

What version of Python are you using?
2.7.3

What version of boar are you using? (Mercurial change id or daily build
date)
boar.16-Nov-2012.tar.gz

Please provide any additional information below.
As far as I can tell the two lines of the output.txt is swapped compared to 
expected.txt

Original issue reported on code.google.com by oscar.y....@gmail.com on 3 Jan 2013 at 3:45

@GoogleCodeExporter
Copy link
Author

Yes. The output is currently dependent upon internal python structures, and 
those seems to have changed in 2.7. Needless to say, output should be 
predictable.

Original comment by ekb...@gmail.com on 3 Jan 2013 at 7:10

  • Changed state: Accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant