Fix regressions URL (#15027)

This commit is contained in:
Anton Kochkov 2019-09-13 16:49:23 +08:00 committed by GitHub
parent e095f8c867
commit 1eb3fe25c9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 8 additions and 9 deletions

View file

@ -67,7 +67,7 @@ test_script:
- radare2 -v
- ps: Install-Product node $env:nodejs_version
- node --version
- git clone https://github.com/radare/radare2-regressions
- git clone https://github.com/radareorg/radare2-regressions
- cd radare2-regressions/new
- ps: $env:pull_owner=($env:APPVEYOR_PULL_REQUEST_HEAD_REPO_NAME -split "/")[0]
- ps: if (-not [string]::IsNullOrWhiteSpace($env:pull_owner)) {cmd /c "(git fetch https://github.com/%pull_owner%/radare2-regressions %APPVEYOR_PULL_REQUEST_HEAD_REPO_BRANCH%:%pull_owner%_%APPVEYOR_PULL_REQUEST_HEAD_REPO_BRANCH% && git checkout %pull_owner%_%APPVEYOR_PULL_REQUEST_HEAD_REPO_BRANCH%) > nul 2>&1 || exit 0"} else {echo "Using master"}

View file

@ -27,7 +27,7 @@ Make sure you are testing using the latest git version of radare2 before submitt
- Please share the binary if it is shareable by drag and dropping it here in a zip archive (mandatory)
- Use asciinema to describe the issue and share the link here (mandatory if u can't share the binary)
- Use code markdown `CODE` to make your code visible
- Or even better, create a Pull-Request for the https://github.com/radare/radare2-regressions containing the test case examples can be found in the t/ folder see for example https://github.com/radare/radare2-regressions/blob/master/t/cmd_search#L7
- Or even better, create a Pull-Request for the https://github.com/radareorg/radare2-regressions containing the test case examples can be found in the t/ folder see for example https://github.com/radareorg/radare2-regressions/blob/master/t/cmd_search#L7
### Additional Logs, screenshots, source-code, configuration dump, ...

View file

@ -24,11 +24,10 @@ try to keep the codebase consistent and clean.
* Check for coding style issues with ```git diff master..mybranch | ./sys/clang-format-diff.py -p1``` and be sure to follow the CODINGSTYLE (more on this in [DEVELOPERS.md](https://github.com/radare/radare2/blob/master/DEVELOPERS.md)).
* Submit the Pull Request(PR) on Github.
* When relevant, write a test for
[radare2-regressions](https://github.com/radare/radare2-regressions) and
[radare2-regressions](https://github.com/radareorg/radare2-regressions) and
submit a PR also there. Use the same branch name in both repositories, so
Travis will be able to use your new tests together with new changes.
AppVeyor (for now) still uses radare/radare2-regressions repo with branch
master. NOTE: when merging PRs, *always* merge the radare2-regressions PR
NOTE: when merging PRs, *always* merge the radare2-regressions PR
first.
# Additional resources

View file

@ -442,7 +442,7 @@ in the code for various reasons.
The source of the radare2 regression test suite can be found in the
following github repository.
```sh
git clone git://github.com/radare/radare2-regressions
git clone git://github.com/radareorg/radare2-regressions
```
See the `README.md` file in that repository for further information.

View file

@ -127,7 +127,7 @@ Look at [CONTRIBUTING.md](https://github.com/radare/radare2/blob/master/CONTRIBU
## Tests
Running `make tests` will fetch the [radare2-regressions](https://github.com/radare/radare2-regressions)
Running `make tests` will fetch the [radare2-regressions](https://github.com/radareorg/radare2-regressions)
repository and run all the tests in order to verify that no changes break any functionality.
We run those tests on every commit, and they are also executed with ASAN

View file

@ -4,6 +4,6 @@ IRED=https://github.com/radare/ired
EXTRAS=https://github.com/radare/radare2-extras
CAPSTONE=https://github.com/radare/radare2-capstone
BINDINGS=https://github.com/radare/radare2-bindings
REGRESSIONS=https://github.com/radare/radare2-regressions
REGRESSIONS=https://github.com/radareorg/radare2-regressions
PR_REGRESSIONS=https://github.com/__USER__/radare2-regressions
[ -z "$1" ] && grep -h $0 | grep -v grep || eval echo \$$1

View file

@ -21,7 +21,7 @@ run tests:
$(MAKE) -C ../radare2-regressions radare2
../radare2-regressions:
cd .. ; git clone -q --depth 1 https://github.com/radare/radare2-regressions
cd .. ; git clone -q --depth 1 https://github.com/radareorg/radare2-regressions
create overlay:
cd ../radare2-regressions ; $(SHELL) ./overlay.sh create