One split per line for MOOSE inputs.

[elementx54]

---

Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

#792

What are the significant changes in functionality due to this change request?

The MOOSE input line is now only split once with the left most = being
used.

Closes #792

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• 1. Review all computer code.
• 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
• 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
• 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in XML block, the node <internalParallel> to True.
• 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• 8. If an analytic test is changed/added is the the analytic documentation updated/added?

[PaulTalbot-INL]

This PR needs a new test (or extension of an existing test) that demonstrates capturing the new behavior.

[elementx54]

There is no test to check MOOSE input files for parsing them correctly, so I couldn't modify an existing test to include multiple equal signs.

[elementx54]

Edit: Added the interface check that didn't exist and made sure the multiple equal signs problem was in the input file.

Should be ready to merge (if it passes).

[elementx54]

I've amended the commit with the requested changes (the two files are gone), and it is ready to restart the tests.

[elementx54]

So the OpenSUSE Tumbleweed test failed because it was never ran. Am I reading that correctly?

[alfoa]

yes

[elementx54]

Ah, so can you re-run that one since it looks like that is the only thing holding up this request? I don't think I can tell it to re-run.

[PaulTalbot-INL]

Actually, the Tumbleweed test is allowed-to-fail and will be discontinued. This is ready to be merged when changes are approved by Andrea, as I see it.

[alfoa]

Checklist passed...

Merging...