Hello, I think this is a great idea! Thanks a lot for fixing all the problems in our examples.
Do you see any problems that could come up if we just run them one by one? We already got a pipeline that allows us to verify jupyter notebooks, but afaik the examples are standalone files with a main function, right? Best regards, Marco Vandana Kannan <[email protected]> schrieb am Mi., 15. Aug. 2018, 23:44: > Hi All, > > Recently we saw that there were quite a few Pylint undefined-variable > errors in MXNet code, a majority of them in the example folder. These > errors highlight that there are paths in the examples that are broken and > these have not been caught during testing. > > These errors are later reported as issues by users. For example, > https://github.com/apache/incubator-mxnet/issues/11278. > > It would be a good idea to include tests for all examples in the nightly > builds (Similar to > incubator-mxnet/tests/nightly/test_image_classification.sh). Side note: We > might have to see what to do about examples that include special setup > instructions or take too long to execute. > > Any thoughts or suggestions on writing these tests, feasibility or > previous attempts at including these tests, would be helpful. > > Thanks, > Vandana >
