udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
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: "{{_35}} failed in the canonical build on lsst-dev failed due to a full disk or quota limit.    {code:java}                   afw: 13.0-94-ga1c4440+6 ....................................................................................:::::  [2017-09-02T07:30:59.486911Z] /home/lsstsw/jenkins/release/lsstsw/miniconda/lib/python2.7/config/libpython2.7.a(posixmodule.o): In function `posix_tempnam':  :::::  [2017-09-02T07:30:59.486972Z] /home/ilan/minonda/conda-bld/work/Python-2.7.12/./Modules/posixmodule.c:7578: warning: the use of `tempnam' is dangerous, better use `mkstemp'  :::::  [2017-09-02T07:30:59.874220Z] /home/lsstsw/jenkins/release/lsstsw/miniconda/lib/python2.7/config/libpython2.7.a(posixmodule.o): In function `posix_tmpnam':  :::::  [2017-09-02T07:30:59.874323Z] /home/ilan/minonda/conda-bld/work/Python-2.7.12/./Modules/posixmodule.c:7631: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'  :::::  [2017-09-02T07:30:59.874362Z] /home/lsstsw/jenkins/release/lsstsw/miniconda/lib/python2.7/config/libpython2.7.a(posixmodule.o): In function `posix_tempnam':  :::::  [2017-09-02T07:30:59.874401Z] /home/ilan/minonda/conda-bld/work/Python-2.7.12/./Modules/posixmodule.c:7578: warning: the use of `tempnam' is dangerous, better use `mkstemp'  :::::  [2017-09-02T07:31:10.858727Z] /tmp/cck8pdsX.s: Assembler messages:  :::::  [2017-09-02T07:31:10.858909Z] /tmp/cck8pdsX.s: Fatal error: can't close tests/ellipse.o: No space left on device  :::::  [2017-09-02T07:31:10.935937Z] scons: *** [tests/ellipse.o] Error 1  :::::  [2017-09-02T07:31:10.941966Z] scons: building terminated because of errors.  ERROR (206 sec).  *** error building product afw.  *** exit code = 2  *** log is in /home/lsstsw/jenkins/release/lsstsw/build/afw/_build.log  *** last few lines:  {code}  "
Answer: 19137.0

User story: "In order to make the jointcal document more readily accessible, I will port the current LaTeX into DMTN-36, using the lsst-tex system."
Answer: 24240.0

User story: "Need to add new rules for developers once the cluster is up and running"
Answer: 40199.0

User story: "Will deploy a new version of kubernetes cluster (v1.7) with Cinder volume attached and NFS server"
Answer: 40200.0

User story: "Push jointcal and meas_mosaic catalogs through validate_drp, generate plots, and look at the results. [~<USER> will do a first cut look to check for obvious problems, before handing off to [~<USER> for the final comparison.    If changes to jointcal are necessary, we can add them to this epic and then re-compare."
Answer: 524159.0

User story: "Run meas_mosaic on the acceptance data, and produce catalogs that are ready to be validated via validate_drp."
Answer: 145815.0

User story: "Run jointcal on the acceptance data, and produce catalogs that are ready to be validated via validate_drp."
Answer: 488266.0
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: "The data that was selected for the jointca/meas_mosaic acceptance test is listed on this website:    https://confluence.lsstcorp.org/display/DM/JointCal+Acceptance+Tests    We need to confirm that it is all available and processed with a recent enough version of the stack, including necessary reference catalogs."
Answer: 49587.0

User story: "The nightly release build is failing on OSX with the error below.  This appears to be due to flake8 line length checking catching constructed shebangs.    {code:java}  =================================== FAILURES ===================================  _____________ FLAKE8-check(ignoring E133 E226 E228 N802 N803 N806) _____________  [gw3] darwin -- Python 3.5.2 /Users/square/jenkins/workspace/release/tarball/osx/10.9/clang-800.0.42.1/miniconda3-4.2.12-7c8e67/build/python/miniconda3-4.2.12/bin/python  /Users/square/jenkins/workspace/release/tarball/osx/10.9/clang-800.0.42.1/miniconda3-4.2.12-7c8e67/build/stack/miniconda3-4.2.12-7c8e67/EupsBuildDir/DarwinX86/pex_policy-13.0-2-g4b114ac/pex_policy-13.0-2-g4b114ac/bin/validate.py:1:111: E501 line too long (142 > 110 characters)    ===================== 1 failed, 83 passed in 3.66 seconds ======================  Global pytest run: failed  Failed test output:  Global pytest output is in /Users/square/jenkins/workspace/release/tarball/osx/10.9/clang-800.0.42.1/miniconda3-4.2.12-7c8e67/build/stack/miniconda3-4.2.12-7c8e67/EupsBuildDir/DarwinX86/pex_policy-13.0-2-g4b114ac/pex_policy-13.0-2-g4b114ac/tests/.tests/pytest-pex_policy.xml.failed  The following tests failed:  /Users/square/jenkins/workspace/release/tarball/osx/10.9/clang-800.0.42.1/miniconda3-4.2.12-7c8e67/build/stack/miniconda3-4.2.12-7c8e67/EupsBuildDir/DarwinX86/pex_policy-13.0-2-g4b114ac/pex_policy-13.0-2-g4b114ac/tests/.tests/pytest-pex_policy.xml.failed  1 tests failed  scons: *** [checkTestStatus] Error 1  scons: building terminated because of errors.  + exit -4  {code}"
Answer: 320.0

User story: "Preparation, presentation, and individual meetings and discussion involving L1 issues at the LSST 2017 Project and Community Workshop."
Answer: 1.0
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: "Processing using Python 2 and Python 3 stacks of the same weekly tag {{w_2017_33}} gave different results for HSC data {{--id visit=6528 ccd=17}} (available in /datasets/hsc/repo)    The Py3 stack fails with the error below, while the Py2 stack can finish processCcd.    {code:java}  processCcd.charImage.measurePsf INFO: PSF determination using 11/12 stars.  processCcd.charImage INFO: iter 2; PSF sigma=1.29, dimensions=(41, 41); median background=7562.40  processCcd.charImage.repair INFO: Identified 812 cosmic rays.  processCcd.charImage.measurement INFO: Measuring 38 sources (38 parents, 0 children)  processCcd.charImage.measureApCorr INFO: Measuring aperture corrections for 23 flux fields  processCcd FATAL: Failed on dataId={'pointing': 991, 'expTime': 200.0, 'visit': 6528, 'ccd': 17, 'field': 'SSP_WIDE', 'filter': 'HSC-Y', 'taiObs': '2014-09-18', 'dateObs': '2014-09-18'}: Unable to measure aperture correction for required algorithm 'modelfit_CModel_initial': only 1 sources, but require at least 2.  {code}        Same part of logs in Py2:  {code:java}  processCcd.charImage.measurePsf INFO: PSF determination using 11/12 stars.  processCcd.charImage INFO: iter 2; PSF sigma=1.28, dimensions=(41, 41); median background=7562.41  processCcd.charImage.repair INFO: Identified 813 cosmic rays.  processCcd.charImage.measurement INFO: Measuring 38 sources (38 parents, 0 children)  processCcd.charImage.measureApCorr INFO: Measuring aperture corrections for 23 flux fields  processCcd.charImage.measureApCorr INFO: Aperture correction for ext_convolved_ConvolvedFlux_1_4_5: RMS 0.126533 from 11  /software/lsstsw/stack/Linux64/meas_algorithms/13.0-18-gc4ad422+4/python/lsst/meas/algorithms/measureApCorr.py:237: RuntimeWarning: invalid value encountered in greater    fluxes > 0.0,  processCcd.charImage.measureApCorr INFO: Aperture correction for modelfit_CModel_exp: RMS 0.046453 from 3  processCcd.charImage.measureApCorr INFO: Aperture correction for ext_convolved_ConvolvedFlux_1_6_0: RMS 0.097525 from 11  {code}  "
Answer: 437823.0

User story: "APIs change, so our builds must change to accomodate them."
Answer: 129987.0

User story: "An unexpected side effect of DM-11514 is that {{pytest}} bakes in the shebang line at package build time:    {code:java}  #!/build/python/miniconda3-4.2.12/bin/python  {code}    This results in the {{pytest}} tarball package not being relocatable:    {code:java}  sh: /smoke/stack/miniconda3-4.2.12-7c8e67/Linux64/pytest/3.2.0/bin/pytest: /build/python/miniconda3-4.2.12/bin/python: bad interpreter: No such file or directory  Global pytest run: failed  mv: cannot stat 'tests/.tests/pytest-base.xml.out': No such file or directory  scons: *** [tests/.tests/pytest-base.xml] Error 1  scons: building terminated because of errors.  script returned exit code 2  {code}    The best course of action may be to require the use of {{shebangtron}} on linux as well as osx."
Answer: 2909.0
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: "When running singleFrameDriver or processCcd with HSC RC data, it's frequent to see warnings like these:     {code:java}  /software/lsstsw/stack/Linux64/meas_algorithms/13.0-18-gc4ad422+4/python/lsst/meas/algorithms/objectSizeStarSelector.py:400: RuntimeWarning: invalid value encountered in less    bad = numpy.logical_or(bad, width < self.config.widthMin)  /software/lsstsw/stack/Linux64/meas_algorithms/13.0-18-gc4ad422+4/python/lsst/meas/algorithms/objectSizeStarSelector.py:401: RuntimeWarning: invalid value encountered in greater    bad = numpy.logical_or(bad, width > self.config.widthMax)  /software/lsstsw/stack/Linux64/meas_algorithms/13.0-18-gc4ad422+4/python/lsst/meas/algorithms/matcherSourceSelector.py:126: RuntimeWarning: invalid value encountered in greater    return sourceCat.get(self.fluxKey)/sourceCat.get(self.fluxSigmaKey) > self.config.minSnr  {code}     [~<USER> thinks they are likely from comparisons with NaNs for flagged sources.  It'd be good to make them go away.     An example data id to reproduce is to run:  {{processCcd.py /datasets/hsc/repo/  --rerun private/username/abcd --id visit=28398 ccd=29}}   Its output is attached in [^example.log]"
Answer: 226148.0

User story: "Update baseline version of LDM-144 to be consistent with operations plans and DM replan architecture. Make additions to LDM-143 to provide descriptions of new categories of purchases, e.g., administrative infrastructure."
Answer: 3.0

User story: "As pointed out in RFC-372, the MasterCal files are better stored separately in {{/datasets/decam/_internal/preprocessed/masterCal/}} rather than living together in the Butler calib repo {{/datasets/decam/_internal/calib/cp201302/}}.  Move the files and reingest if needed. "
Answer: 798113.0

User story: "At the moment, we do not have a clear plan or framework for how we will make measurements of {{verify}} metrics, particularly those that are specific to a single Task's implementation details. Future development of {{ap_verify}} and feature requests for {{verify}} depend on how we intend to handle these metrics.    This ticket is for researching one or more designs for supporting metrics within the Task framework. The result shall be a tech note describing my understanding of the requirements for metrics usage, a summary of what {{verify}} currently supports, and specific proposals for how to incorporate metric measurements into Tasks and/or {{ap_verify}}. The note shall be sent for review to the stakeholders for {{verify}}, {{ap_verify}}, and {{pipe_base}}."
Answer: 78767.0

User story: "Add the build tag to the container name.  This is a necessary pre-req for allowing multiple containers for a single user."
Answer: 24.0

User story: "Involves figuring out to how to connect to the LSST-DB"
Answer: 611695.0

User story: "Involves writing appropriate serialization code for DIAObjects/Sources into databases through the butler."
Answer: 662506.0

User story: "Involves understanding new StorageInterface and formaters being developed for the Butler."
Answer: 662508.0
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: "Pickling support has changed in pybind11 2.2.0. This release introduces the {{py::pickle}} convenience function and deprecates placement new constructors. Unfortunately, it does not seem to trivially work for the complicated {{get/setstate}} in {{daf::base::PropertyList}} (which do Python callbacks). Worse, the old/current way of wrapping doesn't only print deprecation warnings (about the placement new), but also throws:    {code:python}      def checkPickle(self, original):  >       new = pickle.loads(pickle.dumps(original, 2))  E       RuntimeError: return_value_policy = copy, but the object is non-copyable!  {code}    Track down this issue and fix it."
Answer: 8541.0

User story: "In pybind11 2.2.0 a bug was introduced in the STL vector caster line 162 in {{stl.h}} needs to be {{auto const &}} instead of {{auto &}} because otherwise it doesn't work with bit references (which are temporaries).    Report this issue and PR upstream."
Answer: 460535.0

User story: "Add support for {{pytest-cov}} coverage reporting to {{stack-os-matrix}}.  This pytest plugin has support for the Cobertura format.  There is a jenkins plugin that can parse this format:  https://github.com/jenkinsci/cobertura-plugin .  There is not a native pipeline step for this plugin but it has been made callable. Eg.:    {code:java}  step([$class: 'CoberturaPublisher', autoUpdateHealth: false, autoUpdateStability: false, coberturaReportFile: 'foo/**/*.xml', failNoReports: false, failUnhealthy: false, failUnstable: false, maxNumberOfBuilds: 0, onlyStable: false, sourceEncoding: 'ASCII', zoomCoverageChart: false])  {code}    Another option is to use the {{publishHtml}} step to capture the {{pytest-cov}} HTML formatted report."
Answer: 451804.0

User story: "Cloud SQL Proxy is now at 1.10. Updating the LTD Keeper Kubernetes deployment to this should improve reliability.    https://github.com/GoogleCloudPlatform/cloudsql-proxy"
Answer: 1164363.0

User story: "The current {{lsst-the-docs}} Google Container Engine cluster is on a deprecated OS as of September 2017. Upgrade the cluster [according to Google's migration guidehttps://www.google.com/appserve/mkt/p/ALM6Bvxj5JKQb70xcisYnSEWEsXBJIqr8fGezze8xjXW-WAOWohzqJWh08uon8tB2YwKQVJL-nBEE0LSETH0QDP-xWTdYdH2xfvy4eHibwsLCojUV7I4ULuICDihlCo_tI5kBQo67dY9whhS4jySbg] or re-deploy the LTD Keeper and LTD Dasher apps to a new cluster (perhaps a shared one with api.lsst.codes microservices)."
Answer: 150026.0

User story: "Now that there are multiple types of coadds for the different warp types, we should allow specifically requesting PSF-matched templates for image subtraction.   "
Answer: 31644.0

User story: "Adopt https://github.com/jupyterhub/oauthenticator/pull/117"
Answer: 63.0

User story: "During planning stage _Pegasus_ load and parses the DAG representing the workflow multiple times. The goal is to estimate how time of the planning depends on the size of the workflow."
Answer: 22.0
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: "Develop a common SQL schema that represents concrete DataRefs and DataUnits and their relationships that could be used in many different environments, and see if it can be mapped (via views, primarily) to the sort of production database schema imagined by NCSA.    [~<USER> and [~<USER> are working on this together, and hence there will be one ticket for each."
Answer: 77875.0

User story: "Develop a common SQL schema that represents concrete DataRefs and DataUnits and their relationships that could be used in many different environments, and see if it can be mapped (via views, primarily) to the sort of production database schema imagined by NCSA.    [~<USER> and [~<USER> are working on this together, and hence there will be one ticket for each."
Answer: 40240.0

User story: "Define conceptual interfaces and (preliminary) nomenclature for butler redesign.    [~<USER> and [~<USER> are working on this together, and hence there will be one ticket for each.  "
Answer: 77880.0

User story: "Define conceptual interfaces and (preliminary) nomenclature for butler redesign.    [~<USER> and [~<USER> are working on this together, and hence there will be one ticket for each.  "
Answer: 77801.0

User story: "Finish AssocationTask and fully implement unittests for the new task. This could also include incorporating the new task into ap_verify and ap_pipe."
Answer: 48613.0
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: "Currently the {{ci_ctio0m9}} package is using the github backed LFS server.  The typical policy is to use the LSST git-lfs server.  This package should be converted to use that backend."
Answer: 8354.0

User story: "SELECT * FROM Object causes the system to crash. Workers create buffers to send to the czar, and for queries like the above, they quickly generate a very large number of buffers far faster than the czar can read them. This eventually causes the workers to run out of memory and crash."
Answer: 264874.0

User story: "create a Butler StorageInterface subclass that can be used with S3.     also needs simple formatters for testing.     for now do not defer read/write to PosixStorge, pending input from Square about what kind of objects will be serialized & deserialized."
Answer: 28979.0

User story: "per RFC-374"
Answer: 18701.0

User story: "Update run_all script now that data on lsst-dev has moved. Add commented out line at the end showing how one reruns all long direct visits to help people in future."
Answer: 1287.0

User story: "Because the test does not use a temp dir for each test method, rmdir in tearDown can collide:  https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/26515/tests/"
Answer: 33.0

User story: "Current implementation of KILL in qserv accepts thread ID, this is primarily to support mysql client which sends KILL command when Control-C is hit during query execution. For regular users we need to enable query killing by query ID. This would probably need some special syntax as well because we cannot re-purpose KILL command as it is used by regular mysql client."
Answer: 95.0

User story: "KILL QUERY <process id> doesn't kill anything when the process id is found with show processlist; or   {code}   SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST ORDER BY SUBMITTED DESC LIMIT 5\G  {code}    There should be some method of killing a query based on its process if."
Answer: 40444.0

User story: "This may only (always?) happen with the osx / py3 combination. The symptoms are that the console shows:    {code:java}  ### build  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  Rebuild is commencing....stand by; using  -r tickets/DM-11663  {code}    with no further output for a considerable portion of the build but inspecting the node directly shows that the build is progressing normally.  Speculation on possible causes is:    * python stdout buffering  * jenkins agent buffering  * jdk issues -- of note is that the version of java on the osx nodes is at a different patch level"
Answer: 393.0

User story: "Following RFC-379, we need to update the stub packages for numpy, astropy, and matplotlib to use the current versions as minimum versions. We then need to regenerate the conda dependencies for {{lsstsw}} so that the versions installed by end users match the new minimums.    This will happen after v14 is released."
Answer: 97938.0
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: "The {{pytest-cov}} plugin should be enabled to write coverage reports from unit testing. This ticket covers the work to enable per-product coverage testing solely from the unittests associated with that product. This can be enabled as part of normal test execution. It is possible to write coverage results to html, the terminal and XML. XML is needed for Jenkins support -- it may be desirable to default to HTML and terminal reporting but allow Jenkins to enable XML output via an environment variable."
Answer: 403183.0

User story: "Polling must be reimplemented for checking messages for specific topics. Publishers need to use the same object and modify topic as needed, rather than maintaining a publisher for each topic."
Answer: 17542.0

User story: "For the deblender to be optimal in the long term survey, which includes possibly deblending entire images as a single blend, we need to be able to define a bounding box for each source that is a small fraction of the total image size (see the issue created by [~<USER>    at https://github.com/<USER>deblender/issues/14).    Issue DM-11718 has been created to develop an effective algorithm to do this, but will not likely be added to the stack until after testing has been run on a large patch of real HSC images.    This ticket is created to track work that has already been done to test whether or not such an algorithm might be possible, and resulted in [this|https://github.com/lsst-dm/deblender_examples/blob/master/test_bbox.ipynb] ipython notebook, which shows that such a procedure is likely to exist.    It also shows the possibility of performing multi-band object detection in the future, although discussion with [~<USER> indicate that this might be difficult (and/or time consuming) in practice."
Answer: 189.0

User story: "This is in preparation for the 5A pathfinder activity in mid-October."
Answer: 224873.0

User story: "For the deblender to be useful in the long term, which includes possibly deblending entire images as a single blend, we need to be able to define a bounding box for each source that is a small fraction of the total image size (see the issue created by [~<USER>    at https://github.com/<USER>deblender/issues/14).    This ticket will attempt to identify the best algorithm to create an initial bounding box large enough to fit all of the flux for _most_  individual objects, with the possibility of growing the box during optimization if the source appears to need a larger area."
Answer: 277074.0

User story: "At the recent AllHands Meeting, a new method for handling the flurry of connections currently needed was proposed. This story will track its implementation and testing."
Answer: 224876.0

User story: "All forwarders are currently compared in the Audit viewer. A query must be added to examine a specific forwarder and the times/states it evolved through leading up to a failure."
Answer: 224881.0
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: "It is soon time to begin fault injection testing on L1. This capability is needed in case the DMCS or a Foreman must be swapped out during runtime."
Answer: 224895.0

User story: "Software housekeeping."
Answer: 224897.0

User story: "The NCSA foreman code currently differs from the message glossary documentation."
Answer: 224898.0

User story: "This will allow 'Complete Night' testing wherein astronomical files are produced by the forwarders while the Header Service is being completed."
Answer: 224899.0

User story: "Messaging capability is needed to insure synchronizatkoin with the moving parts within the L1 system."
Answer: 224890.0

User story: "Implementing the subscribe function in the forwarder component will allow readouts to proceed in an automated fashion when CCS issues a trigger. Note, for development purposes, the DAQ includes a trigger function."
Answer: 224892.0

User story: "Must be in C++ to mesh seamlessly with DAQ support code."
Answer: 224895.0

User story: "Must be in C++ in order to interface with DAQ API."
Answer: 47829.0

User story: "ProcessDonutTask currently runs a subset of ProcessCcdTask with specific config options, followed by an afterburner of FitDonutTask.  This leads to an unnecessary proliferation of identical icExp files when trying out different config options for the donut fitting subtask.      This story is to refactor the donut pipeline so that ProcessCcdTask gets run once initially (with a specific config), and then FitDonutTask gets promoted to a CmdLineTask which can be run with different config options but always uses the same ProcessCcdTask output as input, eliminating the redundant icExp files (and also providing a small speedup).    ProcessDonutTask can then be eliminated, and DonutDriverTask gets retargeted to parallelize  FitDonutTask instead of parallelizing ProcessDonutTask."
Answer: 34457.0

User story: "Non-ascii character in a docstring in tasks.py"
Answer: 49.0

User story: "In DM-11513 (and RFC-376) we developed a new [lsst/templates|https://github.com/lsst/templates] repository model that takes advantage of Jinja2 and cookiecutter to let us be more precise and deliberate with our templates. The design calls for examples that show rendered files and projects as built by Jinja2/cookiecutter. These examples are committed directly to the templates repo. We need to ensure that the examples stay in sync with the templates, however.    We can implement that with a build system that renders the templates into the lsst/templates repo. Developers of templates can run the build system to refresh examples, and a CI system can also run the build system to ensure that the committed examples are up-to-date.    The build system should be a very simple harness for Jinja2/cookiecutter. Scons might fit the bill, or even Makefiles.    This ticket will implement that system, hook it up to CI for checking, and document how to use it."
Answer: 265274.0
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: "Tasks take multiple {{\-\-id}} arguments to allow data satisfying one or more complex conditions. {{ap_verify}} does not currently have this capability; if the user passes multiple {{\-\-dataIdString}} values, only the last will be used. This behavior should be changed to let users have more of the flexibility they expect from running {{CmdLineTasks}} directly.    Note that this ticket cannot be satisfied by using {{pipe.base.ArgumentParser}}, because that class assumes its program only needs repository (i.e., previously ingested) input.    This ticket may require changes to {{ap_pipe}} to forward multiple IDs to relevant tasks."
Answer: 737316.0

User story: "As reported by [~<USER> on slack, it appears that {{deploy}} is unable to recover a failed miniconda installation:    https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/26482/pipeline/    {code:java}  ::: Deploying Miniconda3 4.2.12 for MacOSX-x86_64  ERROR: File or directory already exists: /Users/square/jenkins/workspace/stack-os-matrix/osx.py3/lsstsw/miniconda  script returned exit code 1  {code}    A possible work around is to remove the {{$LSSTSW/miniconda}} directory if the {{$LSSTSW/miniconda/.deployed}} lock file is absent."
Answer: 1146.0

User story: "Reported upstream: https://issues.jenkins-ci.org/browse/JENKINS-46529"
Answer: 748878.0

User story: "Upstream version 2.2.0 is about to be tagged (https://github.com/pybind/pybind11/issues/953). This release contains a fix for DM-9814."
Answer: 556972.0

User story: "Post merger of DM-11612, junit xml files have been recorded with a non-zero failure count even though the build completed successfully.  There is concern that there is a failure mode in which {{pytest}} observes a test failure but exists {{0}} (confirmed in DM-11693).    As the build is successful, {{lsstswBuild.sh}}'s log printing is not triggered.  It would be useful for debugging purposes to unconditionally artifact all of the build's {{*.log}} files.  Tangentially, saving all of the log files would mean that {{lsstswBuild.sh}}'s could be invoked without the {{--print-fail}}, possibly removing the need to address DM-5887."
Answer: 1474.0

User story: "Various jenkins jobs are generating git changelogs from the {{lsstsw}} and {{buildbot-scripts}} checkouts, which can be confusing to end users. "
Answer: 89372.0

User story: "We currently use a custom lab spawner on the JupyterLab container.  Get rid of that."
Answer: 1931.0
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: In our meeting last week, [~<USER> expressed a desire to be able to make a simple kind of pan/zooming/linked QA plots to investigate some particular question that he and [~<USER> had.  This suggested to me that perhaps a more useful line of development should be in making some simple QA plot "recipes" that anyone can easily define and run in a live notebook  (as opposed to focusing only on a dashboard that aims to reproduce the information the static QA plots).      In this ticket, make an example of this that allows a user to define particular quantities to investigate, and then plot those in linked sky plots.
Answer: 80195.0

User story: "Files created on the docker volume mount should have ownership of {{jenkins-slave:jenkins-slave}} rather than {{centos:centos}}.    {code:java}  [root@jenkins-el7-4 infrastructure]# ls -la /home/jenkins-slave/workspace/sqre/infrastructure/update-cmirror/local_mirror/linux-64/_license-1.1-py27_0.tar.bz2  -rw-r--r-- 1 centos centos 195012 Jun 14 05:26 /home/jenkins-slave/workspace/sqre/infrastructure/update-cmirror/local_mirror/linux-64/_license-1.1-py27_0.tar.bz2    {code}  "
Answer: 4004.0
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: As pointed out in DM-11678, load entire-tract catalogs (~2Gb) into memory in order to make interactive QA plots is not scalable to be able to investigate ~hundreds of tracts at once.  In this ticket, explore & implement an alternative method of persisting the {{pipe_analysis}} catalogs and reading these into memory to make plots.  Two requirements of a solution are that    * Interactive plots can be made on ~500 tracts at a time without overloading typical available RAM  * Such plots can be generated in a reasonable "interactive" amount of time (~few seconds).
Answer: 34120.0

User story: "We have identified 'datashader' as a necessary tool to making interactive QA plots (DM-11405).  The recommended way to use datashader is via the [holoviews package|http://holoviews.org/].  The holoviews way of making/configuring plots is significantly different from both matplotlib and bokeh, so the purpose of this ticket is to become comfortable with holoviews and use it to reproduce a new version of the QA dashboard prototype."
Answer: 9579.0

User story: Tar file in eups scisql 0.3.8 was created with an incorrect prefix.  Builds and "installs" without error, but fails subsequently becuase installed files are in the wrong places.
Answer: 56119.0

User story: "For HSC, I'm currently relying on flat field images taken through a pinhole filter to define the pupil obscuration.  I'm somewhat concerned that this really isn't correct though, since the pupil ought to be defined with respect to an incoming plane wave, not a flat field.  This story is to use a raytracing engine (potentially Zemax, though more likely batoid) to compare simulated pinhole images to simulated pupil masks to get a sense of the potential error incurred by inferring the latter from the former."
Answer: 24562.0

User story: "Work on use cases from the Operations viewpoint (L1 Alert Processing, Offline Batch Production Service, etc)"
Answer: 21702.0

User story: "Butler WG meetings in Aug:  08/03/17  08/10/17  08/16/17   (met during unconference session at LSST2017)  08/24/17  08/31/17"
Answer: 21686.0

User story: "DM-11658 removed a seemingly irrelevant request to install alias packages for python3/python2 support. It seems that this is a global action for the python importer and that packages downstream of pex_exceptions were relying on something else installing the aliases.    Since this is a global compatibility change for all packages, I'm now wondering if we aren't better off calling this once in the {{base}} package. Calling {{install_aliases}} in each package is annoying because the linter gets upset that the command is run before all imports have finished.    I'm sorry I broke the build. It hadn't occurred to me that downstream packages were relying on an earlier package installing this."
Answer: 196.0
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: {code:java}  =================================== FAILURES ===================================  ______________________ GaussianFluxTestCase.testGaussians ______________________  [gw29] linux2 -- Python 2.7.12 /home/lsstsw/jenkins/release/lsstsw/miniconda/bin/python    self = <test_GaussianFlux.GaussianFluxTestCase testMethod=testGaussians>        def testGaussians(self):          """Test that we get correct fluxes when measuring Gaussians with known positions and shapes."""          task = self.makeSingleFrameMeasurementTask("base_GaussianFlux")          exposure, catalog = self.dataset.realize(10.0, task.schema)          task.run(catalog, exposure)          for measRecord in catalog:              self.assertFloatsAlmostEqual(measRecord.get("base_GaussianFlux_flux"),  >                                        measRecord.get("truth_flux"), rtol=3E-3)    tests/test_GaussianFlux.py:67:   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _   ../../stack/Linux64/utils/13.0-8-gb7ca535+1/python/lsst/utils/tests.py:618: in assertFloatsAlmostEqual      testCase.assertFalse(failed, msg="  ".join(errMsg))  E   AssertionError: 99669.5145146 != 100000.0; diff=330.485485371/100000.0=0.00330485485371 with rtol=0.003, atol=2.22044604925e-16  ----------------------------- Captured stdout call -----------------------------  measurement INFO: Measuring 2 sources (2 parents, 0 children)   {code}  
Answer: 68.0

User story: "The weekly release failed last night as {{meas_base}} is broken on master."
Answer: 14629.0

User story: "Enable flake8 testing from pytest."
Answer: 3236.0

User story: "Turn on flake8 testing in pytest"
Answer: 14748.0

User story: "Turn on flake8 testing with pytest."
Answer: 3065.0

User story: "Enable flake8 testing in daf_base with pytest."
Answer: 3077.0

User story: "Turn on flake8 testing within pytest."
Answer: 3094.0

User story: "a base-class formatter storage registry does not separate storages per subclass type properly; need to create a subclass static storage registry."
Answer: 5698.0

User story: "Enable flake8 testing via pytest."
Answer: 865.0

User story: "Namespaces are required to deploy development and production instances in the same cluster.    - https://kubernetes.io/docs/tasks/administer-cluster/namespaces-walkthrough/"
Answer: 35867.0

User story: In DM-10566 we observed condition when proxy disconnected from a "hung" client producing confusing message in the log file. We should try to make timeout handling in proxy to be consistent with mysqld behavior. Would be nice to improve diagnostics as well (and maybe extend it too because current diagnostics is very limited).
Answer: 28527.0
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: "In DM-10805 it was suggested that having ZogyPsfMatchTask inherit from ImagePsfMatchTask is not optimal. ZogyPsfMatchTask inherits from ImagePsfMatchTask in order to utilize its warping functionality. This could be refactored into an ABC and then the two PsfMatchTasks could inherit from that.    This will also require refactoring ZogyPsfMatchConfig to not inherit from ImagePsfMatchConfig."
Answer: 1078944.0

User story: obs_ctio0m9 may or may not be py3 compliant. If it's not, "make it so" ™
Answer: 55873.0

User story: "utils is already flake8-clean. This ticket is to enable pytest auto detection and flake8 testing as part of the normal test target."
Answer: 4342.0

User story: "As DM-11336 changed obs_decam to use the PS1 catalog in LSST format by default, switch {{validate_drp}} DECam test to use HTM reference catalog too.     The new reference catalog may be added to {{validation_data_decam}}"
Answer: 530255.0

User story: "As HSC now uses the PS1 catalog in LSST format by default, switch {{validate_drp}} HSC test to use HTM reference catalog too.     New reference catalog may need to be generated and added to {{validation_data_hsc}}. See DM-9909."
Answer: 272540.0

User story: "Change the default so that python3 is installed when no arguments are specified."
Answer: 4477.0

User story: "Change the default from {{-2}} to {{-3}}."
Answer: 4478.0

User story: "The README should be sufficient to install a cluster from."
Answer: 7657.0

User story: "Update menu extensions for JL 0.27"
Answer: 6396.0

User story: Currently the deblender test data (located [here|https://github.com/lsst/testdata_deblender]) has 5 simulated images created with galsim. Blends are separated by running the stack's `detection` task on them, which estimates positions for the objects and groups them together.    Many of the "blends" detected are not actually blended objects, and many other objects are too faint to be detected by the pipeline (at least in the current catalogs). This makes it difficult to compare the deblender results with the simulated data, where there are a few big and dense blends and a larger number of "blends" whose objects aren't really blended together. The output created in this ticket will be images in all 6 LSST bands, the psf image, the variance in each band, the "truth" catalog, and a set of stack objects (calexps and merged catalogs) for use in the stack.    This is a change in scope from the original description of this ticket, which was just to make the current images more accessible to non-LSST Stack versions of the deblender (ie. the WFIRST deblender).
Answer: 75628.0
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: The minimum requirement is to have squash-db, squash-api and squash-bokeh working together before moving on.    There's still a bug during integration tests:    {code}  File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 508, in send      raise ConnectionError(e, request=request)  requests.exceptions.ConnectionError: HTTPSConnectionPool(host='squash-local.lsst.codes', port=30899): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f102ee90898>: Failed to establish a new connection: [Errno -2] Name or service not known',))    2017-08-23 15:53:40,677 200 GET /AMx (172.17.0.1) 8.13ms  {code}
Answer: 28776.0

User story: "Based on the w_2017_30 run (DM-11185), summarize the computing resources needed to process the RC dataset. For example, execution time in total, in each driver step, in WIDE versus COSMOS. "
Answer: 18531.0

User story: "[verify_metrics|https://github.com/lsst/verify_metrics] has a README with instructions for adding new metrics. This content can now be added to the Sphinx-based package documentation integrated into pipelines.lsst.io."
Answer: 5667.0

User story: "Overall we want to deprecate the use of LTD Mason since we're no longer using LTD Mason to build packages. LTD Conveyor is a centralized library for S3/LTD Keeper clients, and I've used it to build clients into LTD Dasher and Lander projects. However, we still need a generic CLI build uploader to use in CI for general documentation builds. This would specifically replace the ltd-mason-travis CLI.    The goals are:    - Have CLI arguments that are easy to use for ad hoc builds.  - Also have an {{--env=travis}} argument to make Travis-based builds easy (taking advantage of travis environment variables)."
Answer: 358737.0

User story: "Port the ObjectManager directory listing fix from DM-11630 to [ltd-conveyor|https://github.com/lsst-sqre/ltd-conveyor]."
Answer: 20529.0

User story: {{lsst.utils.tests.getTempFilePath()}} creates a predictable file name for a temporary file based on the method and class that call it.  When used as a context, it tries to delete the file on exit.  If the file does not exist at this point, a warning is emitted.  There are cases in the simulations stack where we need to supply the names of temporary files that are not necessarily created.  For example, one of our moving object simulation codes requires a name of a file to which failures are written.  If nothing fails, nothing is written to that file and the file does not exist.  We use {{getTempFilePath()}} to generate the name of this failure log in unittests.  When the failure log does not exist, we get a warning in our stdout.  It would be nice if there was a kwarg in {{getTempFilePath()}} that indicated "we do not care if the file does not get created; do not emit the warning."
Answer: 171073.0

User story: "Changes in squash-bokeh to make it work with the squash-api and squash-deployment, and uniformize README"
Answer: 1463.0
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: "https://issues.jenkins-ci.org/browse/JENKINS-41200  "
Answer: 231423.0

User story: "https://issues.jenkins-ci.org/browse/JENKINS-41502"
Answer: 414551.0

User story: "This is an issue when generating slack notification urls, which will link back to the classic UI."
Answer: 231484.0

User story: The ltd-mason-travis build is showing:    {code}  Traceback (most recent call last):    File "/Users/<USER>.virtualenvs/ltd-mason/bin/ltd-mason-travis", line 11, in <module>      load_entry_point('ltd-mason', 'console_scripts', 'ltd-mason-travis')()    File "/Users/<USER>lsst/_pipelines_lsst_io_build/ltd-mason/ltdmason/traviscli.py", line 58, in run      upload(manifest, product)    File "/Users/<USER>lsst/_pipelines_lsst_io_build/ltd-mason/ltdmason/uploader.py", line 31, in upload      aws_credentials=aws_credentials)    File "/Users/<USER>lsst/_pipelines_lsst_io_build/ltd-mason/ltdmason/uploader.py", line 136, in upload_via_keeper      **aws_credentials)    File "/Users/<USER>lsst/_pipelines_lsst_io_build/ltd-mason/ltdmason/s3upload.py", line 110, in upload      manager.delete_directory(bucket_dirname)    File "/Users/<USER>lsst/_pipelines_lsst_io_build/ltd-mason/ltdmason/s3upload.py", line 353, in delete_directory      assert len(key_objects) > 0  AssertionError  {code}    Turns out the problem is that the {{ObjectManger.list_dirnames_in_directory}} method is suddenly including {{'..'}} as one of the returned directory names, which is an empty directory that can't exist on S3.    I'm already filtering {{'.'}}, so I just need to filter {{'..'}} too.
Answer: 1001.0
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: "[~<USER> found this pug in Python 2 builds with pytest.    {code}  =================================================================================================================== ERRORS ===================================================================================================================  ________________________________________________________________________________________________ ERROR collecting bin.src/dispatch_verify.py _________________________________________________________________________________________________  bin.src/dispatch_verify.py:25: in <module>      from lsst.verify.bin.dispatchverify import main  E   ImportError: No module named bin.dispatchverify  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  ============================================================================================================ 531 tests deselected ============================================================================================================  ================================================================================================== 531 deselected, 1 error in 2.59 seconds ===================================================================================================    {code}    Turns out the issue was that the {{python/lsst/verify/bin/__init__.py}} filename was typo'd and that typo is only seen in Python 2 + pytest+doctest enabled builds."
Answer: 13.0

User story: "https://issues.jenkins-ci.org/browse/JENKINS-44893      {code:java}  Could not create Trilead support class. Using legacy Trilead features  java.lang.ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)   at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)   at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)   at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.createVersion9Instance(TrileadVersionSupportManager.java:51)   at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.getTrileadSupport(TrileadVersionSupportManager.java:32)   at hudson.plugins.sshslaves.verifiers.SshHostKeyVerificationStrategy.getPreferredKeyAlgorithms(SshHostKeyVerificationStrategy.java:68)   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:797)   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)   at java.util.concurrent.FutureTask.run(FutureTask.java:266)   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)   at java.lang.Thread.run(Thread.java:748)  {code}  "
Answer: 578796.0
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: "Port DM-11625 to the HSC branch and release hscPipe 5.4."
Answer: 1659.0

User story: "Add the collection of blueocean plugins to Jenkins.    https://jenkins.io/projects/blueocean/"
Answer: 263.0

User story: "Update JH with current master"
Answer: 129.0

User story: "A utility is needed to remove a git across multiple repos.  The main use case is to remove old weekly release tags."
Answer: 416267.0
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: The "core" of the weekly release, eupspkg/eups distrib tag/git tag/tarballs, completed.  However, the qserv docker image and jupyterlabdemo image builds failed, causing the weekly release to have a failed build status.
Answer: 12036.0

User story: "The qhttp ajax unit test still fails intermittently when run under Jenkins CI.  Logs indicate a timing sensitivity.  Rework this unit test to make it more robust."
Answer: 13064.0

User story: "New scisql version 0.3.8 is out, it fixes issues in running deployment scripts with Python3 (and hence it's needed for Qserv Python3 migration).  "
Answer: 147.0