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

Build is not triggered if diff repository is not set #263

Closed
metaflow opened this issue Nov 18, 2020 · 4 comments
Closed

Build is not triggered if diff repository is not set #263

metaflow opened this issue Nov 18, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@metaflow
Copy link
Collaborator

For example https://reviews.llvm.org/D90930?id=305761
We might need to figure out why that happens an check how many diffs are MIA

@metaflow metaflow added the bug Something isn't working label Nov 18, 2020
@poelmanc
Copy link

poelmanc commented Feb 8, 2021

This just bit me too, e.g. https://reviews.llvm.org/D68682?id=321451. I believed the Repository field was supposed to be left blank per the LLVM Phabricator instructions at https://llvm.org/docs/Phabricator.html:

Leave this first Repository field blank. (We’ll fill in the Repository later, when sending the review.)
...
Leave the Repository field blank. (We previously filled out the Repository for the review request.)

@metaflow
Copy link
Collaborator Author

metaflow commented Feb 23, 2021

I have updated herald rule to trigger check if repository does not match any other known repo:

Repository is not any of rZORG LLVM Github Zorg, rW llvm-www, rLNT LNT, rT test-suite

so now it should trigger on unset repository as well

https://reviews.llvm.org/H511 for "beta" users
https://reviews.llvm.org/H576 for everyone else

@metaflow
Copy link
Collaborator Author

here is an example of build triggered by a revision w/ no repository set https://reviews.llvm.org/D97357?id=325980

@ldionne
Copy link
Collaborator

ldionne commented Feb 25, 2021

Nice, thanks for fixing this. It's been a source of churn in libc++ - glad to see it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants