Hi Liubov,

On Thu, Apr 12, 2018 at 02:24:12PM +0000, Liubov Chuprikova wrote:
> >
> > Great, thanks!  I suppose you could check for specific output contents
> > (via grep, not necessarily 100% identity), but this otherwise all looks
> > good, and is a clear improvement over not having autopkgtests at all.
> >
> I have added simple checks for specific output content. What do you think
> about my last commits? Is it an acceptable way to check or maybe you have
> another idea how it should look like?

Just from reading the shell script it looks fine.  Requiring bash is
also OK.
> Apart from that, could you please help me with *taxblast*. I have tried to
> run it providing SeqAnnot ASN.1 file as required. But I got the same error
> message each time:
> [taxblast] REJECT: Secure socket layer (SSL) has not been properly
> initialized in the NCBI Toolkit.  Have you forgotten to call
> SOCK_SetupSSL()?
> [taxblast] ERROR: [URL_Connect;
> https://www.ncbi.nlm.nih.gov:443/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(
> ]  Failed to connect: Not supported
> ... (here the previous line repets)
> [taxblast] ERROR: [HTTP;
> https://www.ncbi.nlm.nih.gov/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(
> ]  Too many failed attempts (3), giving up
> [taxblast] ERROR: [TaxService]  Service not found
> [taxblast] ERROR: [TaxService]  Cannot connect to service
> [taxblast] ERROR: NI_ServiceGet [no error] ()
> Do you have any suggestions what could be wrong with it?

I hope Aaron will give a more authoritative answer but when I'm reading
SSL I'm getting suspicious:  The test suite needs to be run in a machine
that is disconnected from the internet (similarly when the package is

In some rules file this is somehow faked by using

  export http_proxy=

I'm absolutely not sure that this has any chance to work in the test
suite.  If the test needs network access to succeed than the only way is
to skip that test.

Kind regards



Reply via email to