oneapi-src / oneapi-src/oneapi-ci
Pipeline failure on Gitlab CI
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 111
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone,
I wanted to test the job named build_windows_cpp on GitLab CI by forking this repo (with due fixes as described in the note below) however the bootstrapper doesn't start. No logs except for the extractor:
Notice %ERRORLEVEL% being set to 1 in set installer_exit_code=1
I also tried just calling the bootstrapper to list the components hoping to see basic functionality, to no avail.
Could anyone please take a look and suggest a solution?
Note: runner tags for Windows need to be updated: https://about.gitlab.com/blog/2024/01/22/windows-2022-support-for-gitlab-saas-runners/
Update: I found older download links for version 2023.2 in the commit history, and they work fine. In the meantime I can work with those, but the problem above still remains
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the build_windows_cpp job and the attached job.txt and artifacts.zip, then compare the bootstrapper invocation with the working 2023.2 download links noted in the issue. Check the GitLab Windows runner tags against the linked Windows 2022 support note. Done means the bootstrapper starts and the job runs successfully with current links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, shell
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100