You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Sharath Malladi <sh...@microsoft.com.INVALID> on 2018/06/01 16:46:14 UTC
RE: Re-attempt a failed build on a pull request
Thanks Mariia! I resolved the build failure and pushed new changes. The Appveyor failure now points to test failures - but I see that all pull requests have the test failures. I think this has to do with something external to my pull request now.
-Sharath.
-----Original Message-----
From: Mariia Mykhailova <ma...@microsoft.com.INVALID>
Sent: Wednesday, May 30, 2018 4:52 PM
To: dev@reef.apache.org
Subject: RE: Re-attempt a failed build on a pull request
Sharath,
Travis CI failure looks like a transient issue. Appveyor build, however, failed on the last three iterations of the PR with the same error, so you probably want to look into that.
FileSystem\AzureBlob\AzureCloudBlobClient.cs(83,30): error CS1061: 'CloudBlobDirectory' does not contain a definition for 'ListBlobsSegmented' and no extension method 'ListBlobsSegmented' accepting a first argument of type 'CloudBlobDirectory' could be found (are you missing a using directive or an assembly reference?) [C:\projects\reef\lang\cs\Org.Apache.REEF.IO\Org.Apache.REEF.IO.DotNet.csproj]
FileSystem\AzureBlob\AzureCloudBlobClient.cs(94,28): error CS1061: 'CloudBlobClient' does not contain a definition for 'ListContainersSegmented' and no extension method 'ListContainersSegmented' accepting a first argument of type 'CloudBlobClient' could be found (are you missing a using directive or an assembly reference?) [C:\projects\reef\lang\cs\Org.Apache.REEF.IO\Org.Apache.REEF.IO.DotNet.csproj]
To answer the original question, we don't have access to re-kicking CI builds, so you have to do some trivial commit to the PR to kick them again.
-Mariia
-----Original Message-----
From: Sharath Malladi <sh...@microsoft.com.INVALID>
Sent: Wednesday, May 30, 2018 4:13 PM
To: dev@reef.apache.org
Subject: RE: Re-attempt a failed build on a pull request
Pinging again for help on resolving the build failures on this pull request: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Freef%2Fpull%2F1464&data=02%7C01%7Cmamykhai%40microsoft.com%7C80b555b607004412e06408d5c682ec70%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636633187972634873&sdata=bMMdnTED1AI2MIdDs%2BdwfWg3MK7o8uf2zZzkI3y9hJs%3D&reserved=0
From: Sharath Malladi
Sent: Friday, May 25, 2018 10:35 AM
To: dev@reef.apache.org
Subject: Re-attempt a failed build on a pull request
REEF devs,
I see that the pull request shows that the check for the CI build as failed:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Freef%2Fbuilds%2F383363256&data=02%7C01%7Cmamykhai%40microsoft.com%7C80b555b607004412e06408d5c682ec70%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636633187972634873&sdata=mxLkxCd9b3Lv3yD3pv%2BNOdN5O3M4w0eC7kmAiqOYTYM%3D&reserved=0
The log file does not show any useful information on why it failed. Also, the build had succeeded on a prior iteration<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Freef%2Fbuilds%2F382850420&data=02%7C01%7Cmamykhai%40microsoft.com%7C80b555b607004412e06408d5c682ec70%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636633187972634873&sdata=wjAj7scoa90BGSZR8qiV1fX36a9drdPXm%2BTQnw7r0O4%3D&reserved=0> of the pull request and I suspect that this may be an intermittent issue in the build system. How do I kick off a build again without having to submit another commit?
-Sharath.
Re: Re-attempt a failed build on a pull request
Posted by Scott Inglis <ms...@gmail.com>.
Hi Sharath -- yes those test failures look to be intermittent and not a
result of your change.
On Fri, Jun 1, 2018 at 9:46 AM, Sharath Malladi <
sharathm@microsoft.com.invalid> wrote:
> Thanks Mariia! I resolved the build failure and pushed new changes. The
> Appveyor failure now points to test failures - but I see that all pull
> requests have the test failures. I think this has to do with something
> external to my pull request now.
>
> -Sharath.
>
> -----Original Message-----
> From: Mariia Mykhailova <ma...@microsoft.com.INVALID>
> Sent: Wednesday, May 30, 2018 4:52 PM
> To: dev@reef.apache.org
> Subject: RE: Re-attempt a failed build on a pull request
>
> Sharath,
>
> Travis CI failure looks like a transient issue. Appveyor build, however,
> failed on the last three iterations of the PR with the same error, so you
> probably want to look into that.
>
> FileSystem\AzureBlob\AzureCloudBlobClient.cs(83,30): error CS1061:
> 'CloudBlobDirectory' does not contain a definition for 'ListBlobsSegmented'
> and no extension method 'ListBlobsSegmented' accepting a first argument of
> type 'CloudBlobDirectory' could be found (are you missing a using directive
> or an assembly reference?) [C:\projects\reef\lang\cs\Org.Apache.REEF.IO
> \Org.Apache.REEF.IO.DotNet.csproj]
> FileSystem\AzureBlob\AzureCloudBlobClient.cs(94,28): error CS1061:
> 'CloudBlobClient' does not contain a definition for
> 'ListContainersSegmented' and no extension method 'ListContainersSegmented'
> accepting a first argument of type 'CloudBlobClient' could be found (are
> you missing a using directive or an assembly reference?)
> [C:\projects\reef\lang\cs\Org.Apache.REEF.IO\Org.Apache.
> REEF.IO.DotNet.csproj]
>
> To answer the original question, we don't have access to re-kicking CI
> builds, so you have to do some trivial commit to the PR to kick them again.
>
> -Mariia
>
> -----Original Message-----
> From: Sharath Malladi <sh...@microsoft.com.INVALID>
> Sent: Wednesday, May 30, 2018 4:13 PM
> To: dev@reef.apache.org
> Subject: RE: Re-attempt a failed build on a pull request
>
> Pinging again for help on resolving the build failures on this pull
> request: https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fapache%2Freef%2Fpull%2F1464&
> data=02%7C01%7Cmamykhai%40microsoft.com%7C80b555b607004412e06408d5c682
> ec70%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%
> 7C636633187972634873&sdata=bMMdnTED1AI2MIdDs%2BdwfWg3MK7o8uf2zZzkI3y9hJs%
> 3D&reserved=0
>
> From: Sharath Malladi
> Sent: Friday, May 25, 2018 10:35 AM
> To: dev@reef.apache.org
> Subject: Re-attempt a failed build on a pull request
>
> REEF devs,
>
> I see that the pull request shows that the check for the CI build as
> failed:
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Ftravis-ci.org%2Fapache%2Freef%2Fbuilds%
> 2F383363256&data=02%7C01%7Cmamykhai%40microsoft.com%
> 7C80b555b607004412e06408d5c682ec70%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C1%7C636633187972634873&sdata=mxLkxCd9b3Lv3yD3pv%
> 2BNOdN5O3M4w0eC7kmAiqOYTYM%3D&reserved=0
>
> The log file does not show any useful information on why it failed. Also,
> the build had succeeded on a prior iteration<https://na01.
> safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-
> ci.org%2Fapache%2Freef%2Fbuilds%2F382850420&data=02%
> 7C01%7Cmamykhai%40microsoft.com%7C80b555b607004412e06408d5c682ec70%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636633187972634873&sdata=
> wjAj7scoa90BGSZR8qiV1fX36a9drdPXm%2BTQnw7r0O4%3D&reserved=0> of the pull
> request and I suspect that this may be an intermittent issue in the build
> system. How do I kick off a build again without having to submit another
> commit?
>
> -Sharath.
>