We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm bothered that it wasn't caught by the tests in the compat repo at chevah/compat#700. What shall we do about it?
Maybe Oracle Linux 8 has that library ... I think that we are ok.
These are not actually "tests", but rather builds.
True. Makes sense.
well... what we can do is create separate docker test runs as part of GitHub actions. It will work something like this
That's all
With GitHub Action Artifacts we can "publish" the pythia .tar.gz files in kind of a temporary location
More info about GitHub Artifacts here https://github.com/actions/upload-artifact
Originally posted by @adiroiban in #58 (comment)
The text was updated successfully, but these errors were encountered:
Don't think we have to deal with GitHub artefacts, as we already upload a testing package to our "bin" server after a successful build.
However, what would help immensely would be #47.
Sorry, something went wrong.
dumol
No branches or pull requests
Maybe Oracle Linux 8 has that library ... I think that we are ok.
True. Makes sense.
well... what we can do is create separate docker test runs as part of GitHub actions.
It will work something like this
That's all
With GitHub Action Artifacts we can "publish" the pythia .tar.gz files in kind of a temporary location
More info about GitHub Artifacts here https://github.com/actions/upload-artifact
Originally posted by @adiroiban in #58 (comment)
The text was updated successfully, but these errors were encountered: