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

Modified the codegenTest target to check diff with stable #3909

Merged
merged 1 commit into from
Aug 3, 2024

Conversation

B-rando1
Copy link
Collaborator

@B-rando1 B-rando1 commented Aug 2, 2024

This ensures that the generated code for GOOL tests matches that in stable/gooltest. codegenTest is already in our CI from the looks of it, so this should prevent the cases we've had where build/gooltest doesn't match stable/gooltest.

Next steps:

  • We should add codegenTest_gen to make pr_ready.
    • We probably don't want to add codegenTest to make pr_ready, as it requires that the local machine has the compilers installed for all compiled targets.
  • We still don't have an automatic way of stabilize the build/gooltest folder. We need to add a make codegenTest_stabilize option.

Closes #3678
Contributes to #3387

This ensures that the generated code for GOOL tests matches that in
`stable/gooltest`.  `codegenTest` is already in our CI from the looks of
it, so this should improve our CI.
@JacquesCarette JacquesCarette merged commit 8ca26be into main Aug 3, 2024
5 checks passed
@JacquesCarette JacquesCarette deleted the GoolTestCI branch August 3, 2024 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: Make sure to check gool test artifacts against stable/gooltest
2 participants