Check for err return

[vtjnash]

Pass a reference to the err location instead of the value.

[coveralls]

Pull Request Test Coverage Report for Build 432

• 21 of 21 (100.0%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.05%) to 99.502%

---

Files with Coverage Reduction	New Missed Lines	%
src\ampl_model.jl	1	99.5%

Totals
Change from base Build 428:	0.05%
Covered Lines:	1000
Relevant Lines:	1005

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 432

• 21 of 21 (100.0%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.05%) to 99.502%

---

Files with Coverage Reduction	New Missed Lines	%
src\ampl_model.jl	1	99.5%

Totals
Change from base Build 428:	0.05%
Covered Lines:	1400
Relevant Lines:	1407

---

💛 - Coveralls

[dpo]

Wasn't it passing a reference already? Also it seems strange that there are failures with this change.

[vtjnash]

It was not. It was passing the value of the variable err, a constant set to success? Why is it surprising that failing to check for errors would have resulted in CI that used to mostly pass? I found this problem because it was often failing when I ran the tests locally. I'm surprised that a lot more CI workers passed than I expected. I don't intend to fix this package, just wanted to bring awareness to the problem.