Skip to content

Conversation

@bistline
Copy link
Contributor

No description provided.

bistline and others added 21 commits July 1, 2025 14:33
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.18.8 to 1.18.9.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](sparklemotion/nokogiri@v1.18.8...v1.18.9)

---
updated-dependencies:
- dependency-name: nokogiri
  dependency-version: 1.18.9
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
…iri-1.18.9

Bump nokogiri from 1.18.8 to 1.18.9
Bumps [thor](https://github.com/rails/thor) from 1.3.2 to 1.4.0.
- [Release notes](https://github.com/rails/thor/releases)
- [Commits](rails/thor@v1.3.2...v1.4.0)

---
updated-dependencies:
- dependency-name: thor
  dependency-version: 1.4.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Allow study owners to set order of clustering menus (SCP-6032)
Adjusting size/spacing of study viz settings menus (SCP-6032)
@bistline bistline requested a review from eweitz July 30, 2025 13:25
@eweitz
Copy link
Member

eweitz commented Jul 30, 2025

The build failure looks like a false positive, as we've seen it before.

Total elapsed time: 31 minutes, 2 seconds

### FAILURES and ERRORS ###
*** Yarn test failures ***

*** Rails test failures ***

  StudyValidationTest#test_should_fail_all_ingest_pipeline_parse_jobs:
  RuntimeError: Even after 300 seconds, not all files have been parsed.
Exiting with code: 1
Error: Process completed with exit code 1.

@eweitz eweitz added the build failure: false positive Build error confirmed as false positive. E.g. upstream service has a problem. label Jul 30, 2025
@bistline
Copy link
Contributor Author

The build failure looks like a false positive, as we've seen it before.

Total elapsed time: 31 minutes, 2 seconds

### FAILURES and ERRORS ###
*** Yarn test failures ***

*** Rails test failures ***

  StudyValidationTest#test_should_fail_all_ingest_pipeline_parse_jobs:
  RuntimeError: Even after 300 seconds, not all files have been parsed.
Exiting with code: 1
Error: Process completed with exit code 1.

Yeah, that's a known wonky test occasionally. The other build passed fine: https://github.com/broadinstitute/single_cell_portal_core/actions/runs/16605288043/job/46975418830?pr=2292

@bistline bistline merged commit 84f236f into main Jul 30, 2025
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build failure: false positive Build error confirmed as false positive. E.g. upstream service has a problem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants