-
Notifications
You must be signed in to change notification settings - Fork 4
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
tests flaky right now #175
Comments
And the latest run after my commit to the README: failures for all except macOS 🤪 https://github.com/EMODnet/emodnet.wfs/actions/runs/10898491286/job/30241818460 Is there anything up with the services maybe? |
ah now i get the without fixtures failure locally! |
This is actually really weird. It just worked: sf_data <- emodnet.wfs::emodnet_get_layers(
service = "seabed_habitats_individual_habitat_map_and_model_datasets",
layers = c("dk003069", "dk003070"),
reduce_layers = TRUE
)
#> Loading ISO 19139 XML schemas...
#> Loading ISO 19115 codelists...
#> ✔ WFS client created successfully
#> ℹ Service: "https://ows.emodnet-seabedhabitats.eu/geoserver/emodnet_open_maplibrary/wfs"
#> ℹ Version: "2.0.0" Created on 2024-09-17 with reprex v2.1.0 But right before I got: > sf_data <- emodnet_get_layers(
+ service = "seabed_habitats_individual_habitat_map_and_model_datasets",
+ layers = c("dk003069", "dk003070"),
+ reduce_layers = TRUE
+ )
Space required after the Public Identifier
SystemLiteral " or ' expected
SYSTEM or PUBLIC, the URI is missing
Opening and ending tag mismatch: hr line 0 and body
Opening and ending tag mismatch: body line 0 and html
EndTag: '</' not found
Error: 1: Space required after the Public Identifier
2: SystemLiteral " or ' expected
3: SYSTEM or PUBLIC, the URI is missing
4: Opening and ending tag mismatch: hr line 0 and body
5: Opening and ending tag mismatch: body line 0 and html
6: EndTag: '</' not found
Backtrace:
1. emodnet.wfs::emodnet_get_layers(...)
16. XML (local) `<fn>`(`<chr>`) 🤯 |
@salvafern I'll wait for your feedback and will try again on Thursday. |
As usual, when tests fail, there is an issue with the services, like always , you can check There is nothing special about this, this is a federated system of 40+ services, these go down now and then.... |
Thanks and sorry for not checking the dashboard! |
On my machine, tests pass with and without fixtures. On CI, it failed for every platform with and without fixtures for the try a few hours ago.
@salvafern would you mind running the tests with and without fixtures (just delete the tests/testthat/fixtures folder) on your machine?
The failure for scheduled runs was:
On Ubuntu
The text was updated successfully, but these errors were encountered: