Stream: committers
Topic: local build problem
Andy Stechishin (Jul 05 2017 at 20:26):
I am seeing a build issue locally. Yesterday I did a fresh pull from SVN (blast the directory and perform a clean extract) and then a build at 17:39 Mountain (revision 12188) and it was successful. Later that evening, I did a fresh pull and build in a different directory and now I get the following errors:
[java] ERROR @ Bundle.entry[9].resource.code.coding[1] (line 0, col0): diagnosticreport-example-lri:: Bundle.entry[9].resource.code.coding[1]: Error validating code "28-1" in system "http://loinc.org": Error unmarshalling resource: Year is not valid (0000mmddhhnnss) (src = InstanceValidator)
[java] ERROR @ Bundle.entry[12].resource.code.coding[1] (line 0, col0): diagnosticreport-example-lri:: Bundle.entry[12].resource.code.coding[1]: Error validating code "28-1" in system "http://loinc.org": Error unmarshalling resource: Year is not valid (0000mmddhhnnss) (src = InstanceValidator)
[java] ERROR @ Bundle.entry[9].resource.code.coding[1]: diagnosticreport-example-lri:: Bundle.entry[9].resource.code.coding[1]: Error validating code "28-1" in system "http://loinc.org": Error unmarshalling resource: Year is not valid (0000mmddhhnnss) (src = InstanceValidator)
[java] ERROR @ Bundle.entry[12].resource.code.coding[1]: diagnosticreport-example-lri:: Bundle.entry[12].resource.code.coding[1]: Error validating code "28-1" in system "http://loinc.org": Error unmarshalling resource: Year is not valid (0000mmddhhnnss) (src = InstanceValidator)
[java] This was a Full Build 2.833 759sec 3558MB
[java] FHIR build failure @ Wed, Jul 5, 2017 12:31-0600 0.678 759sec 3558MB
Andy Stechishin (Jul 05 2017 at 20:27):
This is on the same revision # 12188 and I have tried multiple times. Is there a problem with the valueset validation?
Lloyd McKenzie (Jul 05 2017 at 21:12):
I've been having other troubles (slow response time) with the terminology server. Not sure if this is related though.
Paul Knapp (Jul 05 2017 at 21:16):
After an update to the latest build I now have the same error as reported above Andy.
Grahame Grieve (Jul 06 2017 at 07:01):
this is a problem with the terminology server that I've fixed now
Grahame Grieve (Jul 06 2017 at 13:01):
ok I think I have fixed the build now
Last updated: Apr 12 2022 at 19:14 UTC
