Jhrg/hyrax-1963 dmr version bump#320
Conversation
This indicates the change in the serialization algorithm to match the DAP4 specification.
ndp-opendap
left a comment
There was a problem hiding this comment.
My only concern about this is that nothing whatsoever has changed in the DMR XML representation, it's the serialization order that has changed...
hannahilea
left a comment
There was a problem hiding this comment.
lgtm. let's wait to merge until we have a (passing) bes branch ready to merge immediately after.
|
|
People, @ndp-opendap, @hannahilea, Now that we have a BES that is dmrVersion immune, I will put the BES and run its tests when linked with this branch. If they all pass - or if the only failures on my dev machine match those when built with the master of libdap, I will merge this branch. Speak now or forever... ;-) |
|
Fortune favors the bold! (Or, y'know, something like that.) |
I think that there is one test - the GlobalMetadataStoreTest - that fails on the BES with this change. I will double check. |
Here's the problem: |
|
Also, Where we look at one failed test and see: |
|
Interesting; I don't understand how that wasn't caught in Travis when we stripped out dmr version?! The nc ones, also. I wonder if there's something unique about how the tests are running locally for you vs locally for me vs in Travis.... I'm taking a look now. |
|
When I check out this branch locally (m4, Sequoia 15.4.1) and run the bes tests, I do see the |
|
Okay, I added the fix to bes for the I was not able to reproduce the failing netcdf_handler tests, even after manually removing ./testsuite (as discussed in slack). @jgallagher59701, can an you rerun your local tests on this new bes branch and report back if both types of tests are still failing? |
When you removed |
Okay, I think I understand: it was failing on your machine because you hadn't yet removed the stale testsuite? If that's correct, then I think we should be good to go here, now that #BES1232 is merged |
OK, I'm going to merge this... |
|
@jgallagher59701 Out of curiousity - how long until the test.opendap server bumps this version too? |
Once we have a new container, we could do that today. Or maybe tomorrow. I may need to leave early today because I need to run an errand at a place that closes at 4pm. I will work at home after that and I guess I could update test.o.o from there... So, today or tomorrow. |



I changed the dmrVersion XML attribute from 1.0 to 2.0 (the change in DMR serialization makes the two responses incompatible).
I fixed the test baselines. All the tests pass.
This change will break a number of BES tests. So facr, the only change to the baselines has been to change "1.0" to "2.0".