Skip to content

Job Failure - 2025-11-09 #1016

Closed
Closed

Description

@github-actions

Job Failure Report

Date: 2025-11-09 01:51:27 UTC
Workflow Run: https://github.com/hyperlight-dev/hyperlight/actions/runs/19200416888

Details

The scheduled job failed during execution. This issue was automatically created to track the failure. Please check the workflow logs and any uploaded artifacts for more details.

Next Steps

  • Review the workflow logs for error details
  • Download and analyze any crash artifacts if available
  • Determine the root cause of the failure
  • Fix the underlying issue

This issue was automatically created by the CI failure notification system.

Activity

  1. added
    area/testingRelated to tests or testing infrastructure
    release-blockerAdd this label to an issue that should stop a release from running whilst it is open
    area/fuzzingFuzzing related test failures created from weekly CI
    on Nov 9, 2025
  2. github-actions commented on Nov 16, 2025

    @github-actions
    Author

    Job Failed Again

    Date: 2025-11-16 01:51:18 UTC
    Workflow Run: https://github.com/hyperlight-dev/hyperlight/actions/runs/19397416233

    The scheduled job has failed again. Please check the workflow logs and artifacts for details.

  3. added this to the v0.12.0 milestone on Nov 19, 2025
  4. ludfjig commented on Nov 19, 2025

    @ludfjig
    Contributor

    Possibly related to #1000 which is a PR that modified fuzzing right around the fuzzing job started fialign

  5. simongdavies commented on Nov 20, 2025

    @simongdavies
    Member

    Possibly related to #1000 which is a PR that modified fuzzing right around the fuzzing job started fialign

    Looks like it failed with out of space the day before this was merged, I'll take a look at the runner disk size, I also kicked it off again to see if it fails again

  6. simongdavies commented on Nov 20, 2025

    @simongdavies
    Member

    Ran this manually and it passed . Because 2 of the 3 failures showed the runner was out of disk space I have also upped the disk size of the runner from 40GB to 160GB.

  7. removed
    release-blockerAdd this label to an issue that should stop a release from running whilst it is open
    on Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/fuzzingFuzzing related test failures created from weekly CIarea/testingRelated to tests or testing infrastructure

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions