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

frama-c: reactivate CI workflow #5

Closed
pthierry-ledger opened this issue Jul 31, 2024 · 0 comments · Fixed by #4
Closed

frama-c: reactivate CI workflow #5

pthierry-ledger opened this issue Jul 31, 2024 · 0 comments · Fixed by #4
Labels
bug Something isn't working ci-cd About ci-cd related features and enhancement
Milestone

Comments

@pthierry-ledger
Copy link
Member

proof.yml workflow is disabled by now, as it waits for a proper image to be used by cloud CI

@pthierry-ledger pthierry-ledger added bug Something isn't working ci-cd About ci-cd related features and enhancement labels Jul 31, 2024
@pthierry-ledger pthierry-ledger added this to the Sentry-v0.3.0 milestone Jul 31, 2024
pthierry-ledger added a commit that referenced this issue Aug 1, 2024
- Using pthierry38/framac-runner:29 image, based on official
frama-c/framac:29 Debian image
- Add some related fix associated to the usage of a Debian-based bare
image (and not an ubuntu one as Github would like)
- Using dynamic venv for python directly at job level
- Fixed a bug in the autotest meson.build file that used the parseelf.py
script as a program, which lead to failure when using venv. Using the
meson python module find_installation() instead for calling
- increasing the job timeout to 60 minutes (enough by now)
- still a failure in the wp-rcc test, set as expected_fail, opening an
issue instead

Closes #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci-cd About ci-cd related features and enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant