Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dashboard: allow using repo alias as an argument to #syz test #2265

Closed
xairy opened this issue Nov 23, 2020 · 2 comments · Fixed by #4539
Closed

dashboard: allow using repo alias as an argument to #syz test #2265

xairy opened this issue Nov 23, 2020 · 2 comments · Fixed by #4539
Assignees

Comments

@xairy
Copy link
Collaborator

xairy commented Nov 23, 2020

Currently syzbot reports on the upstream tree include:

git tree:       upstream

But then using #syz test: upstream 4d02da97 isn't acceptable and leads to an error.

@riking
Copy link

riking commented Nov 26, 2020

Specifically, the suggestion is to define it as an alias for https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git or wherever mainline moves to in the future.

@a-nogikh a-nogikh self-assigned this Jul 27, 2023
@a-nogikh
Copy link
Collaborator

a-nogikh added a commit to a-nogikh/syzkaller that referenced this issue Feb 29, 2024
In our reports, we sometimes supply short alias names for the
repositories. It was confusing for our users why they could not use that
same short name in patch testing requests.

Closes google#2265.
a-nogikh added a commit to a-nogikh/syzkaller that referenced this issue Feb 29, 2024
In our reports, we sometimes supply short alias names for the
repositories. It was confusing for our users why they could not use that
same short name in patch testing requests.

Closes google#2265.
github-merge-queue bot pushed a commit that referenced this issue Mar 5, 2024
In our reports, we sometimes supply short alias names for the
repositories. It was confusing for our users why they could not use that
same short name in patch testing requests.

Closes #2265.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants