I saw the same behaviour for https://build.gluster.org/job/regression-on-demand-full-run/47/consoleFull as well. In both the cases the common pattern is if a test was retried but overall the job succeeded. Is this a bug which got introduced recently? At the moment, this is blocking us to debug any tests which has been retried but the job overall succeeded.
*01:54:20* Archiving artifacts*01:54:21* ‘glusterfs-logs.tgz’ doesn’t match anything*01:54:21* No artifacts found that match the file pattern "glusterfs-logs.tgz". Configuration error?*01:54:21* Finished: SUCCESS I saw the same behaviour for https://build.gluster.org/job/regression-on-demand-full-run/47/consoleFull as well. On Sat, Aug 11, 2018 at 9:40 AM Ravishankar N <ravishan...@redhat.com> wrote: > > > On 08/11/2018 07:29 AM, Shyam Ranganathan wrote: > > ./tests/bugs/replicate/bug-1408712.t (one retry) > I'll take a look at this. But it looks like archiving the artifacts > (logs) for this run > ( > https://build.gluster.org/job/regression-on-demand-full-run/44/consoleFull) > > was a failure. > Thanks, > Ravi > _______________________________________________ > maintainers mailing list > maintainers@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers >
_______________________________________________ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
