Skip to content

[Wisp] thread leak when wisp off #431

[Wisp] thread leak when wisp off

[Wisp] thread leak when wisp off #431

Re-run triggered March 4, 2025 02:12
Status Success
Total duration 3m 39s
Artifacts 33

main.yml

on: pull_request
Prerequisites  /  Check Commit Message
2m 53s
Prerequisites / Check Commit Message
Prerequisites  /  Prerequisites
43s
Prerequisites / Prerequisites
Matrix: linux-aarch64 / build
Matrix: linux-x64 / build
Matrix: windows-x64 / build
Matrix: riscv64 / build
Matrix: linux-aarch64 / test
Matrix: linux-x64 / test
Matrix: windows-x64 / test
Remove bundle artifacts
3s
Remove bundle artifacts
Fit to window
Zoom out
Zoom in

Annotations

24 warnings
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Prerequisites / Prerequisites
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
riscv64 / build (release)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / build (debug)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / build (release)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
windows-x64 / build (release)
Failed to restore: Failed to GetCacheEntryDownloadURL: Unable to make request: ETIMEDOUT If you are using self-hosted runners, please make sure your runner has access to all GitHub endpoints: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github
windows-x64 / build (release)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
linux-x64 / test (langtools/tier1)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (jdk/tier1 part 2)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (jdk/tier1 part 1)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (jdk/tier1 part 3)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (hs/tier1 common)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (hs/tier1 gc)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (hs/tier1 runtime)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (hs/tier1 compiler)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (hs/tier1 serviceability)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (dragonwell/jdk feature)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
linux-x64 / test (dragonwell/hs feature)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Artifacts

Produced during runtime
Name Size
results-linux-aarch64-dragonwell_jdk_feature
485 KB