[Memory Safety] Memory Safety Analysis Report - Unable to Access Artifacts

[github-actions[bot]]

Memory Safety Analysis Report

Date: 2026-03-09
Commit: 78fa6d5 on branch master
Triggered by: push
Workflow Run: #22874214995
Commit Message: "allow calling lp().restore_x() only in case the number of column in lp( ) remained the same: it might grow"

---

⚠️ Report Generation Failed

Status: The Memory Safety Analysis workflow completed successfully, but this reporting workflow was unable to access the generated artifacts.

Issue Details

The workflow run 22874214995 completed with the following jobs:

• ✅ ASan Build & Test - Completed successfully (33min 14s)
• ✅ UBSan Build & Test - Completed successfully (34min 21s)
• ✅ Memory Safety Summary - Completed successfully (6s)

Artifacts Available:

• asan-reports (308 KB)
• ubsan-reports (308 KB)

Problem: This reporting workflow lacks GitHub API authentication (GH_TOKEN) required to download workflow artifacts and access job logs. The GitHub API returned:

• Artifact downloads: Authentication required
• Job logs: "Must have admin rights to Repository" (403 Forbidden)

---

🔧 Recommendations to Fix

Option 1: Configure GH_TOKEN (Recommended)

Add authentication to the reporting workflow:

env:
  GH_TOKEN: $\{\{ github.token }}

This grants the workflow permission to download artifacts from the triggering run.

Option 2: Use Workflow Job Summaries

Modify the Memory Safety Analysis workflow to write sanitizer findings to GitHub job summaries using:

- name: Write Summary
  run: |
    cat summary.md >> $GITHUB_STEP_SUMMARY

Job summaries may be accessible without authentication and appear directly in the Actions UI.

Option 3: Store Results as Workflow Outputs

Instead of artifacts, output sanitizer findings as workflow outputs or write to a known repository location that this workflow can access.

Option 4: Grant Artifact Read Permissions

Configure repository workflow permissions to allow cross-workflow artifact access:

permissions:
  actions: read
  contents: read

---

📊 What We Know

Based on job metadata:

• Both ASan and UBSan builds completed successfully
• Build times: ~33-34 minutes each
• Artifacts were generated (combined size: ~616 KB)
• No build failures reported

However, without access to the actual sanitizer reports, we cannot determine:

• Number of memory safety findings
• Severity and types of issues (buffer overflows, use-after-free, etc.)
• Affected source files and line numbers
• Whether this represents a regression or improvement

---

🎯 Immediate Action Required

1. Configure authentication for this workflow to enable artifact downloads
2. Re-run this reporting workflow once authentication is configured
3. Review the raw artifacts manually at: Workflow Run #22874214995

---

Metadata

• Workflow Run ID: 22874214995
• Repository: Z3Prover/z3
• Branch: master
• SHA: 78fa6d5
• Event: push
• Status: Workflow succeeded, but reporting failed due to missing authentication

---

This is an automated report generated by the Memory Safety Analysis Report Generator workflow. For questions or issues, please review the workflow configuration.

AI generated by Memory Safety Analysis Report Generator

• expires on Mar 16, 2026, 9:31 PM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-03-16T21:31:21.312Z.

Closed by Workflow