The job was canceled because "_3_0" failed.

Edit a study edit open study Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy 1 Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission process. Provide ONLY if the project has already been submitted to EBI.\nStudy na

Edit a study add external customer information Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy 1 Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission process. Provide ONLY if the project has already been submitted

Edit a study when data release strategy is Not Applicable does not error when setting strategy to Open Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy: Never Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission pr

Pooling from page directly user can pool from different tubes to stock and standard mx tubes Failure/Error: expect(find('.barcode_list')).to have_content '1234567890123' expected to find text "1234567890123" in ""

Pooling from sample manifest page user can pool from different tubes to stock and standard mx tubes Failure/Error: expect(page).to have_content 'Scanned: 5' expected to find text "Scanned: 5" in "Test\nStudies\nProjects\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nMultiplex Pools New\nThis page allows you to scan in multiple tubes of tagged samples to generate a new multiplexed library. Tube can contain single or multiple samples. Just scan or type each barcode into the 'Scan tube' box in turn.\nTag clash report\ni7 - i5 -\nSample Sample1 Library Scanned Tube NT1O\nSample Sample2 Library Scanned Tube NT2P\nSample Sample3 Library Scanned Tube NT3Q\nSample Sample4 Library Scanned Tube NT4R\nScan tube\nNT1O\nRemove from list\nNT2P\nRemove from list\nNT3Q\nRemove from list\nNT4R\nRemove from list\nNT5S\nRemove from list\nCreate stock multiplexed tube\nCreate standard multiplexed tube\nPrint labels\nCount\nBarcode printer\nHelp\nWellcome Sanger Institute\nA tool from LIMS and Informatics\nSequencescape 0.0.0 [test] HEAD@3c046e4\nLOCAL\nfv-az735-11"

Batches controller reordering requests Failure/Error: expect(request_list.all('tr').first).to eq(third_request) expected: #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[3]"> got: #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]"> (compared using ==) Diff: @@ -1 +1 @@ -#<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[3]"> +#<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">

Labwhere reception user can scan plates into the reception Failure/Error: expect(find('.barcode_list')).to have_content plate.human_barcode expected to find text "SQPD-1" in ""

Labwhere reception displays the correct labwhere error messages Failure/Error: expect(page).to have_content 'LabWhere User does not exist' expected to find text "LabWhere User does not exist" in "Test\nStudies\nProjects\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nAsset barcodes can't be blank\nLabwhere Reception\nUser barcode or swipecard\nScan location barcode\nScan plate or tube\nHelp\nWellcome Sanger Institute\nA tool from LIMS and Informatics\nSequencescape 0.0.0 [test] HEAD@3c046e4\nLOCAL\nfv-az735-11"

Process completed with exit code 1.