Investigating.

On Nov 26 2023, at 12:32 am, Mikhail Khludnev <m...@apache.org> wrote:
> Pardon
>
> On Sun, Nov 26, 2023 at 11:28 AM Gautam Worah <worah.gau...@gmail.com 
> (mailto:worah.gau...@gmail.com)> wrote:
> > I think you meant to send it to d...@solr.apache.org 
> > (mailto:d...@solr.apache.org)?
> >
> > On Sun, Nov 26, 2023 at 12:24 AM Mikhail Khludnev <m...@apache.org 
> > (mailto:m...@apache.org)> wrote:
> > > Hello
> > > It's rather like a logical error in crave pull. How to work around it?
> > > + status=0
> > > + ./crave pull '**/build/**/test/TEST-*.xml' '**/*.events' 'heapdumps/**' 
> > > '**/hs_err_pid*'
> > > Error: rsync: [sender] change_dir "/tmp/src/solr/heapdumps" failed: No 
> > > such file or directory (2)
> > > rsync error: some files/attrs were not transferred (see previous errors) 
> > > (code 23) at main.c(1682) [Receiver=3.1.3]
> > > rsync: [Receiver] write error: Broken pipe (32)
> > >
> > > + exit 0
> > > ---------- Forwarded message ---------
> > > From: Apache Jenkins Server <jenk...@builds.apache.org 
> > > (mailto:jenk...@builds.apache.org)>
> > > Date: Sun, Nov 26, 2023 at 11:17 AM
> > > Subject: [JENKINS] Solr » Solr-Check-9.x - Build # 5949 - Still Failing!
> > > To: <bui...@solr.apache.org (mailto:bui...@solr.apache.org)>
> > >
> > >
> > >
> > > Build: https://ci-builds.apache.org/job/Solr/job/Solr-Check-9.x/5949/
> > > No tests ran.
> > > Build Log:
> > > [...truncated 1490 lines...]
> > > ERROR: Step ‘Publish JUnit test result report’ failed: No test report 
> > > files were found. Configuration error?
> > > Email was triggered for: Failure - Any
> > > Sending email for trigger: Failure - Any
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: builds-unsubscr...@solr.apache.org 
> > > (mailto:builds-unsubscr...@solr.apache.org)
> > > For additional commands, e-mail: builds-h...@solr.apache.org 
> > > (mailto:builds-h...@solr.apache.org)
> > >
> > >
> > >
> > >
> > > --
> > > Sincerely yours
> > > Mikhail Khludnev
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
> --
> Sincerely yours
> Mikhail Khludnev
>
>

Reply via email to