give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I'm rebuilding {{lsst_distrib}} from a clean {{newinstall}} for the {{d_2018_10_30}} tag (though this isn't necessarily when the problem started). This is on macOS High Sierra 10.14.    {code}    [ 123/125 ]  validate_drp 16.0-13-ge350b0c+2 ...    ***** error: from /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/build.log:  tests/test_load_json.py::ParseJsonJob::testPlotMetricsFromJsonJob    /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/matplotlib/axes/_axes.py:6462: UserWarning: The 'normed' kwarg is deprecated, and has been replaced by the 'density' kwarg.      warnings.warn("The 'normed' kwarg is deprecated, and has been "    /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/matplotlib/axes/_base.py:3129: UserWarning: Attempted to set non-positive xlimits for log-scale axis; invalid limits will be ignored.      'Attempted to set non-positive xlimits for log-scale axis; '    /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/matplotlib/axes/_base.py:3129: UserWarning: Attempted to set non-positive xlimits for log-scale axis; invalid limits will be ignored.      'Attempted to set non-positive xlimits for log-scale axis; '    -- Docs: http://doc.pytest.org/en/latest/warnings.html  =============== 1 failed, 74 passed, 7 warnings in 34.42 seconds ===============  Coverage.py warning: No data was collected. (no-data-collected)  Global pytest run: failed with 1  Failed test output:  Global pytest output is in /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/validate_drp-16.0-13-ge350b0c+2/tests/.tests/pytest-validate_drp.xml.failed  The following tests failed:  /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/validate_drp-16.0-13-ge350b0c+2/tests/.tests/pytest-validate_drp.xml.failed  1 tests failed  scons: *** [checkTestStatus] Error 1  scons: building terminated because of errors.  + exit -4  eups distrib: Failed to build validate_drp-16.0-13-ge350b0c+2.eupspkg: Command:          source "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/eups/2.1.4/bin/setups.sh"; export EUPS_PATH="/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb"; (/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/build.sh) >> /Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/build.log 2>&1 4>/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb/EupsBuildDir/DarwinX86/validate_drp-16.0-13-ge350b0c+2/build.msg  exited with code 252  {code}    The relevant failure is:    {code}  self = <test_load_json.ParseJsonJob testMethod=testPlotMetricsFromJsonJob>        def testPlotMetricsFromJsonJob(self):          """Does plotting the metrics run and produce the correct filenames?                This could be loosely seen as a test of the outputPrefix handling              and thus DM-11410, it's a rather incomplete one because the chain              of wrapping functions is different.              """          job = load_json_output(self.jsonFile)          filterName = get_filter_name_from_job(job)            noOutputPrefixFiles = ['check_astrometry.png',                                 'check_photometry.png',                                 'PA1.png',                                 'validate_drp.AM1_D_5_arcmin_17.0_21.5_mag.png',                                 'validate_drp.TE1_D_1_arcmin.png',                                 'validate_drp.TE2_D_5_arcmin.png']          # test with no output prefix.          plot_metrics(job, filterName)          for filename in noOutputPrefixFiles:  >           assert os.path.exists(filename), "File not created: %s"%filename  E           AssertionError: File not created: validate_drp.AM1_D_5_arcmin_17.0_21.5_mag.png  E           assert False  E            +  where False = <function exists at 0x104561bf8>('validate_drp.AM1_D_5_arcmin_17.0_21.5_mag.png')  E            +    where <function exists at 0x104561bf8> = <module 'posixpath' from '/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-  scipipe-fcd27eb/lib/python3.6/posixpath.py'>.exists  E            +      where <module 'posixpath' from '/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/pos  ixpath.py'> = os.path    tests/test_load_json.py:95: AssertionError  ----------------------------- Captured stdout call -----------------------------  latex was not able to process the following string:  b'validate_drp.AM1 measured: 6.6 marcsec (passed)'      {code}    I'm wondering if ultimately the issue is that my {{~/.matplotlib/matplotlibrc}} has matplotlib using LaTeX to render labels, but for that to work with a label like {{"validate_drp.AM1 measured: 6.6 marcsec (passed)"}}.    Is there a way we can dynamically configure matplotlib in our code to not use the LaTeX string renderer? Otherwise, we'll need to document a warning to users that their personal matplotlibrc files may not be compatible with {{lsst}}.
Answer: 557702.0