hcho3 opened a new pull request #12189: Drop dmlc-core commits that break MXNet 
build
URL: https://github.com/apache/incubator-mxnet/pull/12189
 
 
   ## Description ##
   Partially reverts apache/incubator-mxnet#12129 by dropping commits 
dmlc/dmlc-core#409 and dmlc/dmlc-core#399.
   
   These commits by themselves are fine, but they tigger double free memory 
error inside CSVIter. In #12139, the CSVIter test crashed on CentOS. The memory 
error has been inside CSVIter but remained undetected until a recent 
modification of CSVParser.
   
   ## Checklist ##
   ### Essentials ###
   Please feel free to remove inapplicable items for your PR.
   - [x] Changes are complete (i.e. I finished coding on this PR)
   - [x] All changes have test coverage:
   - Unit tests are added for small changes to verify correctness (e.g. adding 
a new operator)
   - Nightly tests are added for complicated/long-running ones (e.g. changing 
distributed kvstore)
   - Build tests will be added for build configuration changes (e.g. adding a 
new build option with NCCL)
   - [x] Code is well-documented: 
   - For user-facing API changes, API doc string has been updated. 
   - For new C++ functions in header files, their functionalities and arguments 
are documented. 
   - For new examples, README.md is added to explain the what the example does, 
the source of the dataset, expected performance on test set and reference to 
the original paper if applicable
   - Check the API doc at 
http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
   - [x] To the my best knowledge, examples are either not affected by this 
change, or have been fixed to be compatible with this change
   
   ### Changes ###
   - [x] Revert dmlc-core to last working point
   - [ ] Selective add dmlc-core commits so that the double-free memory error 
is not triggered
   
   ## Comments ##
   - This is a temporary measure. We'll need to come back to CSVIter and 
address memory error. Address Sanitizer reveals double free issues in CSVIter.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to