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

Add test-powerpc to CI #139

Open
ianfixes opened this issue Nov 13, 2020 · 1 comment
Open

Add test-powerpc to CI #139

ianfixes opened this issue Nov 13, 2020 · 1 comment
Labels
CI Continuous Integration enhancement New feature or request help wanted Extra attention is needed SheepShaver affects SheepShaver executable

Comments

@ianfixes
Copy link
Member

With the example results file from #102, the test file SheepShaver/src/kpx_cpu/src/test/test-powerpc.cpp can somehow be leveraged to conduct automated tests.

It's unclear how this test should be built and executed, beyond the observations that:

  1. the ppc-testresults.dat file (MD5 3e29432abb6e21e625a2eef8cf2f0840) should be stored in compressed form as ppc-testresults.dat.bz2 (MD5 60172863f951c72e1ee7e01d54ed6db3) -- 36MB vs 4.6MB
  2. the test file seems to want to be provided as an input argument to the test program
  3. the test file is handled differently depending on architecture (and I haven't dug into it further)
@ianfixes ianfixes added enhancement New feature or request help wanted Extra attention is needed CI Continuous Integration SheepShaver affects SheepShaver executable labels Nov 13, 2020
@ianfixes
Copy link
Member Author

@asvitkine I saw your username on the directory with the test file, any insight you can offer will go directly into a README

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration enhancement New feature or request help wanted Extra attention is needed SheepShaver affects SheepShaver executable
Projects
None yet
Development

No branches or pull requests

1 participant