close the pr; wait 10 seconds (to let github deliver the closed message) then
open the pr...
(or log into the jenkins instance and press play on the job)
On 6/11/20 8:17 PM, David Mollitor wrote:
Hello,
I am trying to re-run a test:
http://130.211.9.232/job/hive-precommit/job/PR-1082/
Maybe
Hello,
I am trying to re-run a test:
http://130.211.9.232/job/hive-precommit/job/PR-1082/
Maybe it's a permission issue, but I don't see a way to manually do it. We
really need a way though GitHub to re-launch the tests.
On Wed, Jun 10, 2020 at 3:07 PM David Mollitor wrote:
> Great, thanks!
Great, thanks!
What triggers these builds? Do we need to add something to branch-2,
branch-3 projects to get this to trigger there?
On Wed, Jun 10, 2020 at 3:03 PM Zoltán Haindrich wrote:
> its on cooldown...5 builds/day/branch
> http://34.66.156.144:8080/job/hive-precommit/job/PR-1082/
>
> On
its on cooldown...5 builds/day/branch
http://34.66.156.144:8080/job/hive-precommit/job/PR-1082/
On June 10, 2020 6:55:45 PM GMT+02:00, David Mollitor wrote:
>Zoltán,
>
>Even a PR against master is only running Travis.
>
>https://github.com/apache/hive/pull/1082
>
>On Wed, Jun 10, 2020 at 12:52 PM
Zoltán,
Even a PR against master is only running Travis.
https://github.com/apache/hive/pull/1082
On Wed, Jun 10, 2020 at 12:52 PM David Mollitor wrote:
> Hey Zoltán,
>
> Also in regard to that PR, it only ran the travis build "mvn clean
> install -DskipTests -q -Pitests"
>
> What does this b
Hey Zoltán,
Also in regard to that PR, it only ran the travis build "mvn clean install
-DskipTests -q -Pitests"
What does this branch require (and 3.x) to enable running of tests?
Thanks.
On Wed, Jun 10, 2020 at 11:36 AM David Mollitor wrote:
> Hey Zoltán,
>
> Yes. That is correct. Commu
Hey Zoltán,
Yes. That is correct. Community recently put out a 2.x release. This is
in case someone wishes to release a new one.
Does that have any bearing on re-running tests?
Thanks.
On Wed, Jun 10, 2020 at 11:32 AM Zoltán Haindrich wrote:
> That pr seems to be for branch-2 and not maste
That pr seems to be for branch-2 and not master
On June 10, 2020 5:17:19 PM GMT+02:00, David Mollitor wrote:
>Zoltan,
>
>I just tried to close/re-open a PR and I don't believe it triggered a
>new
>CI run:
>
>https://github.com/apache/hive/pull/1076
>
>Thanks.
>
>On Wed, Jun 10, 2020 at 10:59 AM D
Zoltan,
I just tried to close/re-open a PR and I don't believe it triggered a new
CI run:
https://github.com/apache/hive/pull/1076
Thanks.
On Wed, Jun 10, 2020 at 10:59 AM David Mollitor wrote:
> Hey Zoltan,
>
> Can you please research a way to initiate it from the GitHub interface? I
> have
Hey Zoltan,
Can you please research a way to initiate it from the GitHub interface? I
have a strong feeling we're going to need such a capability regularly.
Thanks.
On Wed, Jun 10, 2020 at 9:29 AM Zoltan Haindrich wrote:
> Hey
>
> you could:
> * push new commits to the branch
>- this will
Hey
you could:
* push new commits to the branch
- this will create a new merge with the current master
* login in to the jenkins instance: and launch a new build of that PR
* close&re-open the pr: will re-emit the github event triggering the testrun
* login in to the jenkins instance: and press
Hey Zoltan,
What is the process to trigger a new CI build on GitHub if a previous one
failed on a flaky test. timeout, or something of that nature?
Thanks.
12 matches
Mail list logo