Re: [RFS] art-nextgen-simulation-tools

[Andreas Tille]

Hi Nilesh,

On Sun, Feb 23, 2020 at 11:52:37AM +0530, Nilesh Patra wrote:
> I have fixed art-nextgen-simulation-tools failed tests in debci.
> It builds fine in a clean chroot, with passing autopkgtests.
> I have pushed my changes to team repo here[1].
> Needs review and sponsorship.
> 
> [1]: https://salsa.debian.org/med-team/art-nextgen-simulation-tools

Sponsored your changes - thanks a lot, Andreas.

-- 
http://fam-tille.de

Re: [RFS] art-nextgen-simulation-tools

[Nilesh Patra]

On Sun, 23 Feb 2020, 13:55 Andreas Tille,  wrote:

> Hi Nilesh,
>
> On Sun, Feb 23, 2020 at 11:52:37AM +0530, Nilesh Patra wrote:
> > I have fixed art-nextgen-simulation-tools failed tests in debci.
> > It builds fine in a clean chroot, with passing autopkgtests.
> > I have pushed my changes to team repo here[1].
> > Needs review and sponsorship.
> >
> > [1]: https://salsa.debian.org/med-team/art-nextgen-simulation-tools
>
> Sponsored your changes - thanks a lot, Andreas.
>

Thanks! \o/

Re: Failure in autopkgtest for loki (Was: Working tests seem to exist for epcr)

[Liubov Chuprikova]

Hi Andreas,

I ran loki's tests on my machine in sbuild environment, and I got no
errors. As I understand it, the loki.dat file has to exist after "prep"
steps. I added an "ls" into the run-unit-test to check this. Also, I turned
on the build-time tests that are more or less the same as for the
autopkgtest. The build-time tests also finish successfully for me.

Could you, please, rerun pbuilder again?

Regards,
Liubov

On Sat, 22 Feb 2020 at 08:09, Andreas Tille  wrote:

> Hi Pranav,
>
> On Fri, Feb 21, 2020 at 07:30:09PM +0530, Pranav Ballaney wrote:
> > > You are perfectly welcome.  On one hand I see this as my duty as a
> > > (pontential) GSoC mentor.  On the other hand your level of contribution
> > > shows that you are really dedicated to the task and I'd love to support
> > > this.
> >
> > Yes, it's my first time contributing to open source, so I'm really
> excited
> > about the opportunities this work provides, both of open source
> > contributions, as well as being part of something as prestigious as GSoC!
>
> I need to admit that your contributions had a high level and its hard to
> believe for me that its your first time contributing to open source.
> I'm always happy to see competent students in GSoC.
>
> > > In principle an sbuild setup - provided that it also has something like
> > > a hook that is triggering the autopkgtest running in a chroot - should
> > > lead to the same results.
> >
> > I just use the
> > autopkgtest .  -- schroot unstable-amd64-sbuild
> > command to run the tests. I'll try automating the process with pbuilder
> and
> > see if I can replicate the issue.
> > It will make things easier for me as well, for tests I write in the
> future.
>
> My personal experience with schroot is that I never managed to setup
> sbuild to my satisfaction.  The configuration steps always seemed to be
> quite complex.  Thus I sticked to pbuilder (which I by chance started
> using first).
>
> > > Just take your time.  In case you might be blocked it can help if you
> > > look into another package.  Liubov had announced to possibly have a
> look
> > > at the weekend and sometimes it helps to have an additional pair of
> > > eyeballs.  Sorry, for my "feature" to always stumble about issue. ;-)
> > >
> >
> > Yes, I have started working on tests for fastlink, but it might take
> longer
> > this time because my mid-semester exams are starting, so I will be busy
> > with academics the next two weeks.
>
> I can only repeat what I said to previous GSoC students:  Please always
> give your study and your exams preference over GSoC work.  In case there
> is urgent stuff for you to do just tell me and all is fine.
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>
>

Request for sponsoring changes in idba

[Pranav Ballaney]

Hi,
I have added autopkgtests for idba .
(Closes #909716 )

I need a few suggestions on how these tests can be improved.

   1. The test data can be generated using the sim_reads command that comes
   with the package, but for some reason, it isn't installed when the package
   is built. I am being able to use it if I build the package from source on
   my machine, but within the testing chroot, autopkgtest reports that this
   command is not found. If this command can be used while testing, the
   downloads required for testing will be reduced from the current 25MB to a
   mere 1.5MB, because the rest of the data can be generated as required. For
   now, I have generated and added all the files manually, and included the
   code used to generate this data in a README file inside
   debian/tests/test_data, if it becomes possible to run these while testing
   at a later stage.
   2. To copy the test_data to a temp folder inside the testing chroot, I
   have added an install file inside the debian folder. Is this the right way
   to do it?

I have also updated the changelog (and marked the bug resolved) and added a
README.test file inside debian.
Please let me know if I missed out anything, and if not, please review and
sponsor these changes.

Regards,
Pranav
ᐧ

Re: Failure in autopkgtest for loki (Was: Working tests seem to exist for epcr)

[Pranav Ballaney]

Hi Andreas,

On Sat, Feb 22, 2020 at 12:39 PM Andreas Tille  wrote:

> Hi Pranav,
>
> I need to admit that your contributions had a high level and its hard to
> believe for me that its your first time contributing to open source.
> I'm always happy to see competent students in GSoC.
>

Thank you :)

My personal experience with schroot is that I never managed to setup
> sbuild to my satisfaction.  The configuration steps always seemed to be
> quite complex.  Thus I sticked to pbuilder (which I by chance started
> using first).
>

While reading the debian-med email archive from last year, I found some
helpful links from Liubov on this subject, and a few videos you had posted
links to.
Thanks to the both of you for that!


> I can only repeat what I said to previous GSoC students:  Please always
> give your study and your exams preference over GSoC work.  In case there
> is urgent stuff for you to do just tell me and all is fine.
>

Thanks a lot for understanding. I could squeeze in a few hours today, so I
have added tests for one more package. Please take a look whenever it is
convenient for you.

Regards,
Pranav
ᐧ