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

Recover or re-create ppc-testresults.dat.bz2 #102

Closed
ianfixes opened this issue Mar 28, 2019 · 8 comments · Fixed by #140
Closed

Recover or re-create ppc-testresults.dat.bz2 #102

ianfixes opened this issue Mar 28, 2019 · 8 comments · Fixed by #140
Labels
docs Anything documentation-related enhancement New feature or request help wanted Extra attention is needed meta Ops, chores, placeholders, decisions SheepShaver affects SheepShaver executable
Milestone

Comments

@ianfixes
Copy link
Member

From doc/PowerPC-Testsuite.md:

It is recommended that you first run the tester on a native PowerPC platform to generate a results file. For reference, here is the [[this>projects/ppctester/files/ppc-testresults.dat.bz2|PowerPC Emulator Tester results file]] I use for SheepShaver. This was generated with AltiVec tests enabled. This is for revision 1.30+ of the file. md5sum is: ''3e29432abb6e21e625a2eef8cf2f0840''.

We should do that, and save the file here for posterity.

(Note: this issue was originally emaculation/SheepShaver#10)

@ianfixes ianfixes added enhancement New feature or request help wanted Extra attention is needed docs Anything documentation-related meta Ops, chores, placeholders, decisions SheepShaver affects SheepShaver executable labels Mar 28, 2019
@ianfixes ianfixes added this to the Stabilization milestone Mar 28, 2019
@rakslice
Copy link
Contributor

rakslice commented Oct 15, 2020

What even is this testsuite? Is it actually in the codebase somewhere?

@rakslice
Copy link
Contributor

Oh, I get it, it's test-powerpc.cpp.

It basically has two modes; if you run it on a native PowerPC system, it tests the local CPU and writes the results to a file. Otherwise, it takes a results file, does a test on the emulated CPU (using the JIT if you pass --jit first) and compares the results with the results file.

It has no concept of anything but real (one-to-one with the host system) memory addresses.

@ianfixes
Copy link
Member Author

Correct, this issue is to track getting/generating a copy of that results file so that we could actually test against it in this repo.

@rakslice
Copy link
Contributor

@ianfixes
Copy link
Member Author

This was a good lead, but upon downloading every version they had I didn't get the right MD5

$ md5 ppc-testresults*
MD5 (ppc-testresults (1).dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3
MD5 (ppc-testresults (2).dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3
MD5 (ppc-testresults (3).dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3
MD5 (ppc-testresults (4).dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3
MD5 (ppc-testresults (5).dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3
MD5 (ppc-testresults.dat.bz2) = 60172863f951c72e1ee7e01d54ed6db3

I wonder if @cebix or @FreeBSD-pzn can comment on its suitability of this other version of the test file

@rakslice
Copy link
Contributor

Try md5summing the file in the archive :D

@ianfixes
Copy link
Member Author

🎉 👍 🥇 !!!

@ianfixes
Copy link
Member Author

This is excellent, I hadn't imagined that this file would ever turn up.

I've opened #139 to track making actual use of this file as part of CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Anything documentation-related enhancement New feature or request help wanted Extra attention is needed meta Ops, chores, placeholders, decisions SheepShaver affects SheepShaver executable
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants