-
Notifications
You must be signed in to change notification settings - Fork 541
Let contributors know why tests are failing #9916
Copy link
Copy link
Open
Labels
Component: ContainersAnything related to cloudy Dataverse, shipped in containers.Anything related to cloudy Dataverse, shipped in containers.Feature: NoneNo user-facing feature in particularNo user-facing feature in particularType: Suggestionan ideaan ideaUser Role: Hackathon ParticipantCore developers, frequent contributors, drive-by contributors, etc.Core developers, frequent contributors, drive-by contributors, etc.
Metadata
Metadata
Assignees
Labels
Component: ContainersAnything related to cloudy Dataverse, shipped in containers.Anything related to cloudy Dataverse, shipped in containers.Feature: NoneNo user-facing feature in particularNo user-facing feature in particularType: Suggestionan ideaan ideaUser Role: Hackathon ParticipantCore developers, frequent contributors, drive-by contributors, etc.Core developers, frequent contributors, drive-by contributors, etc.
Type
Projects
Status
No status
Status
⚠️ Needed/Important
Currently we show them a red x with no details of which tests failed.
This is because https://jenkins.dataverse.org is behind a firewall.
Probably we will try to build something public using GitHub Actions. Unfortunately, out of the box, GitHub Actions doesn't show details of failures to the public. (See https://github.com/gdcc/api-test-runner/actions/runs/6126277581 for example.) The hope is to publish a report somehow, as discussed at https://dataverse.zulipchat.com/#narrow/stream/379673-dev/topic/github.20test.20reports/near/385654854 . See progress by @poikilotherm at https://github.com/IQSS/dataverse/compare/9916-action-reports