Skip to content

Fix SV-COMP packaging of the jar artifact; report the package version - #94

Merged
nils-loose merged 1 commit into
devfrom
fix/package-flat-artifact
Oct 20, 2026
Merged

nils-loose merged 1 commit into
devfrom
fix/package-flat-artifact

Conversation

@nils-loose

Copy link
Copy Markdown
Contributor

The tag build of svcomp27-rc1 failed in the package job (missing built artifact file). Since #92 the build job uploads only symbolic-executor/lib/symbolic-executor.jar, and actions/upload-artifact drops the directories of a single-file upload.

  • package-svcomp.sh also accepts symbolic-executor.jar at the artifact root.
  • run-swat.sh -v prints the package version from BUILD_INFO.txt (e.g. svcomp27-rc1), falling back to the old output (1).

Checked locally: the package built from a flat artifact directory passes check-svcomp-package.sh in docker.io/ubuntu:26.04 (version svcomp27-rc1, Z3 5.3.1, smoke test passed).

🤖 Generated with Claude Code

…kage version

actions/upload-artifact drops the directories of a single-file upload, so the
package job finds symbolic-executor.jar at the artifact root. run-swat.sh -v
now prints the version from BUILD_INFO.txt instead of the constant "1".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nils-loose nils-loose added this to the SV-COMP 2027 milestone Oct 20, 2026
@nils-loose
nils-loose merged commit 2bd2bbf into dev Oct 20, 2026
10 of 12 checks passed
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.

1 participant