Skip to content

Conversation

@lhoguin
Copy link
Contributor

@lhoguin lhoguin commented Oct 7, 2025

The first commit enables problem matchers. Subsequent commits are varied fixes found after enabling problem matchers.

@mergify mergify bot added the make label Oct 9, 2025
In order to get the right subdirectory for GH to find
our files we use `sed` to modify paths in the output.

We use `pipefail` to make sure failures are propagated.

We use `NON_DETERMINISTIC` to make sure our paths are
full and not just the file.erl.

We disable styling in non-parallel CT runs. This is
needed in order to pick up errors. Currently these
errors will not be annotated directly in PRs, a
pending OTP PR will improve that. Parallel CT runs
write GH annotations directly.
There's one test that kills the queue on purpose.
UTF-8 validation that used xmerl_ucs:from_bin/1
now uses unicode:characters_to_binary/3.
Identical clause was found in the same function.
@lhoguin lhoguin force-pushed the loic-problem-matchers branch from 7e93397 to a1960c8 Compare October 16, 2025 15:13
Changing the path to a non-existent /ws2 still succeeded.
Other tests properly check connecting.
@lhoguin lhoguin force-pushed the loic-problem-matchers branch 2 times, most recently from e7fa9a8 to f05b18d Compare October 17, 2025 09:41
@lhoguin lhoguin changed the title DO NOT MERGE CI: Enable Erlang problem matchers Enable Erlang problem matchers Oct 17, 2025
@lhoguin lhoguin changed the title Enable Erlang problem matchers CI: Enable Erlang problem matchers Oct 17, 2025
@lhoguin lhoguin marked this pull request as ready for review October 17, 2025 11:08
@michaelklishin michaelklishin merged commit cd85cc9 into main Oct 23, 2025
865 of 867 checks passed
@michaelklishin michaelklishin deleted the loic-problem-matchers branch October 23, 2025 00:55
@michaelklishin
Copy link
Collaborator

@lhoguin this kind of annotations on PRs certainly looks promising :)

I assume we want to see how it goes for main before backporting?

@lhoguin
Copy link
Contributor Author

lhoguin commented Oct 23, 2025

Yeah and have 4.2 release first. We may also not want the xmerl commit in 4.2 and below as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants