-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functional test failing, but github job doesn't fail #586
Comments
@gkc were you able to get the tests to fail (in the same way locally)? I'm trying to replicate, and it seems the tests are running OK against trunk. |
I fixed the tests last week. I'll make a branch for you and add a deliberately failing test |
@gkc I've gone back to #0805d1c which is where things were when that GitHub Actions job ran, and the tests pass locally for me, but there's no sign of any attempt to run
|
@gkc running these locally I get a 0 exit code despite tests failing So this is a |
Carrying 2SP into PR89 as @gkc wants to do a little more testing before we open a ticket with the Dart team. |
@gkc I think we have an answer at dart-lang/test#2248 (comment) Looks like this is happening when we hit an We now have some head scratching to do in order to figure out correct behaviour under test versus in production (whilst the VM team do the same for the more general case of exit handling). |
Aha! Yes |
Evidence here that our test pack as whole will now, correctly, fail if there is any individual test failure. |
Describe the bug
When tests are failing in the test step of the functional_tests_at_onboarding_cli job defined in at_libraries.yaml, the overall job does not fail and so the test failures are not flagged on the PR
Steps to reproduce
See https://github.com/atsign-foundation/at_libraries/actions/runs/9191223708/job/25277175158 for example. Noticed in the course of working on #582
Expected behavior
If the tests fail then the job should fail
The text was updated successfully, but these errors were encountered: