You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running down a test failure in conda-forge/libnetcdf-feedstock#154, ncdump/tst_bom.sh and ncdump/tst_nccopy4.sh failed, with odd diffs. They were running concurrently, and it turns out the problem is that both test scripts write temporary output to tmp.cdl.
I'll also note that tmp.cdl is mentioned in ncdump/run_back_comp_tests.sh (but commented out). The file is also removed (but not created?) in ncdump/tst_nccopy5.sh.
There are also some occurrences in nczarr_test/run_nccopyz.sh and nczarr_test/run_nczarr_fill.sh. I'm not sure if that's potentially problematic or not.
The text was updated successfully, but these errors were encountered:
re: Issue Unidata#2551
Ryan May identified the use of a common scratch file (tmp.cdl)
across multiple test shell scripts in ncdump directory
and the nczarr_test directory.
This sometimes causes errors because of race conditions
between those scripts.
I renamed those common files to avoid the race condition. I
also did some further checking and found some additional,
similar conflicts and fixed those. Also did some minor cleanup
of unused files.
Tests fixed:
ncdump: run_back_comp_tests.sh tst_bom.sh tst_nccopy4.sh tst_nccopy5.sh
nczarr_test: git df master -- run_nccopyz.sh run_nczarr_fill.sh run_scalar.sh
Running down a test failure in conda-forge/libnetcdf-feedstock#154,
ncdump/tst_bom.sh
andncdump/tst_nccopy4.sh
failed, with odd diffs. They were running concurrently, and it turns out the problem is that both test scripts write temporary output totmp.cdl
.I'll also note that
tmp.cdl
is mentioned inncdump/run_back_comp_tests.sh
(but commented out). The file is also removed (but not created?) inncdump/tst_nccopy5.sh
.There are also some occurrences in
nczarr_test/run_nccopyz.sh
andnczarr_test/run_nczarr_fill.sh
. I'm not sure if that's potentially problematic or not.The text was updated successfully, but these errors were encountered: