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

curious if it's possible to run matoya tests in CI #115

Open
wants to merge 21 commits into
base: stable
Choose a base branch
from

Conversation

bmcnett
Copy link

@bmcnett bmcnett commented Jun 6, 2024

curious if it's possible to run matoya tests in CI

curious if it's possible to run matoya tests in CI
@bmcnett bmcnett added the 1. Coding Feature has been described inside of the parsec branch, and you are coding on it. label Jun 6, 2024
windows won't even nmake yet
this test may have not been working for a few years, now
… valid condition)

this test shouldn't fail if sleep took longer than expected (that's a valid condition)
just a random guess for why this is failing for linux / mac
…n error

until i can figure out why it's failing, i can have it fail without an error
derpity derp
more derping
on push or label-add, it tests if 'Test Matoya' flag is set
@bmcnett bmcnett added Test Matoya This runs the Matoya tests in CI and removed 1. Coding Feature has been described inside of the parsec branch, and you are coding on it. labels Jun 6, 2024
bmcnett added 12 commits June 6, 2024 14:03
wonder if this works
need steps, apparently
…s for no good reason

these tests seem to hit rate limiters on a website, and fail sometimes for no good reason
printing messages in github's preferred format
tests are now deterministic (except those for MTY_*Random*)
let's use a format github likes
a little simpler
added a test that fails if the recent JSON fix is absent
can this be removed?
can this be removed, too?
environment variable "seed" should be "MATOYA_TEST_SEED"
@bmcnett bmcnett self-assigned this Jun 9, 2024
@bmcnett bmcnett added the 2. Review requested You have coded your code, and can now be reviewed. label Jun 18, 2024
@Namaneo
Copy link

Namaneo commented Sep 6, 2024

Doesn't look like tests are running, are they supposed to before we can review?

@dvijayak
Copy link
Member

dvijayak commented Sep 9, 2024

This work should IMHO be delayed until our matoya fork is merged into the Parsec repo. At that point, setting up MTY tests to run in CI should be immune to these weird CI oddities that Julien might be hinting at.

Moved label to L1 in light of this, but if you disagree, feel free to respond and bring the label back to L2.

@dvijayak dvijayak added 1. Coding Feature has been described inside of the parsec branch, and you are coding on it. and removed 2. Review requested You have coded your code, and can now be reviewed. labels Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Coding Feature has been described inside of the parsec branch, and you are coding on it. Test Matoya This runs the Matoya tests in CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants