Skip to content

Conversation

@grisumbras
Copy link
Member

Hopefully this will work better than the previous approach.

I had to split directories into main and extra, because otherwise tracking what comes from where becomes onerous.

@pdimov
Copy link
Member

pdimov commented Oct 10, 2025

This looks good. But I don't want the stack trace. Catch the exception, print the message, and exit.

@grisumbras grisumbras force-pushed the fix/cycles-restrict branch 3 times, most recently from 2b2cfdd to 0879009 Compare October 10, 2025 15:14
@pdimov
Copy link
Member

pdimov commented Oct 10, 2025

I don't think that vprint(0 is what we want there, because (a) fatal errors should go to stderr and (b) they shouldn't be suppressed by -q.

@pdimov pdimov merged commit dad7ac2 into boostorg:develop Oct 10, 2025
134 of 140 checks passed
@pdimov
Copy link
Member

pdimov commented Oct 10, 2025

Perfect, thank you.

Unfortunately the print to stderr appears before the normal output in GHA's log:

Error: Dependency cycle detected: geometry -> graph -> geometry
Installing: config, headers, ../tools/boost_install, ../tools/build, ../tools/cmake, geometry
Installing: config, range, rational, concept_check, math, core, static_assert, iterator, numeric/conversion, endian, throw_exception, type_traits, predef, variant, graph, assert, algorithm, mpl, lexical_cast, tokenizer, tuple, container, serialization, integer, qvm, function_types, multiprecision, thread, array, variant2, fusion, any, polygon
Error: Process completed with exit code 1.

I tried sys.stdout.flush(), but it didn't help.

Any ideas how this could be fixed?

@grisumbras
Copy link
Member Author

The only thing I can suggest is to add 2>&1 to the command.

@grisumbras grisumbras deleted the fix/cycles-restrict branch October 10, 2025 17:37
@pdimov
Copy link
Member

pdimov commented Oct 10, 2025

Yes, this output buffering seems to be a "feature" of Github Actions, there's nothing to be done from our side.

But I'm starting to think that vprint should have actually gone to stderr to begin with, as depinst doesn't print any "program output" per se, only status messages, which (one might argue) are stderr material.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants