Repository navigation
Community setup - #5
Merged
Merged
Conversation
- CONTRIBUTING.md for pull requests: how a pull request gets merged, what CI checks, what a maintainer checks by hand (clean-room scan, review, GPU test). - Pull-request template with the clean-room statement as a checkbox; CODEOWNERS. - ROADMAP.md, COMPATIBILITY.md (0.6.0, how to add your game), the game compatibility issue form and docs/TESTING-OTHER-GAMES.md. - README: community status and a Contributing section. - tools/ci: line-ending check, the Ray Reconstruction plugin's CPU tests and the CPU Python test set, for the CI workflow and for local runs. Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
…dows runner Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
…tep at its first failing command The plugin's build script defaults VSDEVCMD to Visual Studio 18 Community; the runner has Visual Studio 2022, so the step now sets VSDEVCMD from VSINSTALLDIR. Every multi-line step also sets $PSNativeCommandUseErrorActionPreference, so a failing command fails the step at once instead of only the step's last command counting. Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
build.py runs its compiles inside the output folder, so a relative --out (as BUILDING.md gives it: --out out\rr-proxy) was resolved twice and the compiler could not write its object files. The folder is now made absolute right after the arguments are read. Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
phantoslayer21
marked this pull request as ready for review
November 13, 2026 03:18
5 tasks done
- CONTRIBUTING: CI's REUSE lint does not fail on a missing SPDX line (the `**` rule in REUSE.toml covers every file); say so, and say a missing header is caught in review. - README, COMPATIBILITY: Borderlands 4 Model M is "tested with 0.4.5", not a 0.6.0 result. The "about 1.6 ms" figure cites clean/installer/tests/logs/bl4-rr-only.log; the Ray Reconstruction mode and the WrongGPU version of that run are not recorded in the excerpt. - RELEASING: the release page lists the zip's SHA-256 and SHA256SUMS.txt in the zip lists every file's, as the 0.6.0 notes say. - ROADMAP: Hogwarts Legacy: state the observed fact; the cause is not known. - README, PR template: the same list for when a GPU test is required as in CONTRIBUTING. The template links CONTRIBUTING.md absolutely and says the clean-room statement is made once, in the first pull request. - tools/ci/run_python_tests.py: keep the output of a timed-out test module (TimeoutExpired carries bytes). - ci.yml: cancel superseded runs on pull requests only, so every main commit keeps its result. - tools/ci/run_proxy_core_tests.py: the docstring says that build.py --no-tests still builds and runs the WARP-based probe and hook tests. Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sets WrongGPU up as a community project: CI on every pull request, a written contribution flow, a roadmap, and the
game-compatibility page back in the repository.
What's in it
.github/workflows/ci.yml, Windows runner, actions pinned to released versions; no GPU jobs). Thescripts it runs (
tools/ci/) can also be run locally. Every multi-line step stops at its first failing command.reuse==5.0.2) andtools/ci/check_line_endings.py(files storedexactly as committed:
.gitattributesis* -text, no CR LF).launcher-core, coexist-core, source size, wording), the Ray Reconstruction plugin built with
--no-testsand itsCPU test executables (
tools/ci/run_proxy_core_tests.py), and the CPU Python test set(
tools/ci/run_python_tests.py: everyclean/**/test_*.pyexcept the modules that need a GPU device).review by someone who did not write it, a GPU test on an RX 9000-series card when the change touches kernels, the
runtime, the front end or the Ray Reconstruction plugin, then the owner merges), the clean-room statement, sign-off
(DCO 1.1), and a rule for numbers in documents.
(
* @phantoslayer21).game compatibility issue form (label
game-compatibility) and docs/TESTING-OTHER-GAMES.md back.Timings appear only where a measurement record exists (Borderlands 4).
on a public commit, with the package's SHA-256 on the release page (the zip) and in
SHA256SUMS.txtinside the zip(every file), and every figure traced to its measurement record.
issue (Build WrongGPU from a fresh clone and report where the guide breaks #2), and a Contributing section.
clean/rr_f/proxy/tools/build.py: a relative--outis made absolute, because the compiles run inside theoutput folder. Without it the first
clcall failed with C1083.Tested
--outand passes.Not tested
build.pyis path handling only.Settings still to set (proposals; nothing was changed)
main: require the two CI checks once this pull request has shown them green (their exactnames are in the first passing run).
main.Signed-off-by: phantoslayer21 156617979+phantoslayer21@users.noreply.github.com