Oh, and I just realized that it's actually testing the caching behavior on *two* different remote json-ld contexts (schema.org and schema.org/docs/jsonldcontext.json). So we could cut the 8 seconds down to 4 by removing the second url, if that's necessary.
On Tue, Jun 5, 2018 at 4:10 PM, Hans Brende <[email protected]> wrote: > Hi Lewis. > > Yes, that test ensures that ANY23-336 has been fixed by loading a remote > json-ld context 1000 times (or failing after 60 seconds). Loading the > context the first time is probably the major bottleneck there; each > subsequent load should be cached. > > On Tue, Jun 5, 2018 at 3:25 PM, lewis john mcgibbney <[email protected]> > wrote: > >> Hi Folks, >> Anyone have insight into why this is? >> >> [INFO] Running org.apache.any23.extractor.rdf.JSONLDExtractorTest >> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >> 7.841 s - in org.apache.any23.extractor.rdf.JSONLDExtractorTest >> >> Thanks >> Lewis >> >> -- >> http://home.apache.org/~lewismc/ >> http://people.apache.org/keys/committer/lewismc >> > >
