Unreadable compiler output
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- testing-qa
Research direction
Open impl/compiler_log_formatter.ipp around line 155 and inspect the checkpoint formatting in relation to the surrounding test output. Make the requested formatting adjustment, then run the relevant Boost.Test compiler-output tests or reproduce the shown failure to verify that each last checkpoint stays with its test suite output.
Written by the indexing model from the issue text.
Description
Hey!
There is quite unreadable output of test errors. I mean that line where talked about "last checkpoint" sticks together with output of next test suite:
Running 5 test cases...
unknown location(0): fatal error: in "DbAccess_AccountMappingTests/DatabaseMapping_Account": Wt::Dbo::backend::PostgresException: ERROR: new row for relation "accounts" violates check constraint "is_retail_for_only_client_account"
DETAIL: Failing row contains (19, 0, 2022-12-30 15:25:50.432222, nccName321, 0, 1000000.00000000, 1, 1111, ALFA, 0, 1, null, null, 1, t, 0, t, 0.1, null, f, , , null, f, f, 0, 1000000.00000000, f, f, , , , 1000000.00000000, 0, f, 1, null, f, , f, f, 2, 0, 0, 1, f, f, f, , t, 6636, 0, t, PrincipalFirmId, PrincipalTradeClearingAccountId, PrincipalFirmId, ClientTrustedCode, null, 1000000.00000000, 0, f, t, t, , 0.00000000, 0, f, f).
/home/dmitry-trebushnikov/main/Sources/Trading/src/TradingTestUtils.cpp(847): last checkpoint
Dbo.Session: Session exiting with 1 dirty objects
unknown location(0): fatal error: in "DbAccess_AccountMappingTests/DatabaseMapping_AccountWithCurrencies_FromDbCache": Wt::Dbo::backend::PostgresException: ERROR: duplicate key value violates unique constraint "accounts_name_and_owner_firm_id_key"
DETAIL: Key (name, owner_firm_id)=(name222, 1) already exists.
/home/dmitry-trebushnikov/main/Sources/Trading/src/DbAccess/DatabaseTestFixture.cpp(187): last checkpoint
I think it is much more consistent to stick it with its test suite output and separate from next:
Running 5 test cases...
unknown location(0): fatal error: in "DbAccess_AccountMappingTests/DatabaseMapping_Account": Wt::Dbo::backend::PostgresException: ERROR: new row for relation "accounts" violates check constraint "is_retail_for_only_client_account"
DETAIL: Failing row contains (19, 0, 2022-12-30 15:28:29.370916, nccName321, 0, 1000000.00000000, 1, 1111, ALFA, 0, 1, null, null, 1, t, 0, t, 0.1, null, f, , , null, f, f, 0, 1000000.00000000, f, f, , , , 1000000.00000000, 0, f, 1, null, f, , f, f, 2, 0, 0, 1, f, f, f, , t, 6636, 0, t, PrincipalFirmId, PrincipalTradeClearingAccountId, PrincipalFirmId, ClientTrustedCode, null, 1000000.00000000, 0, f, t, t, , 0.00000000, 0, f, f).
/home/dmitry-trebushnikov/main/Sources/Trading/src/TradingTestUtils.cpp(847): last checkpoint
Dbo.Session: Session exiting with 1 dirty objects
unknown location(0): fatal error: in "DbAccess_AccountMappingTests/DatabaseMapping_AccountWithCurrencies_FromDbCache": Wt::Dbo::backend::PostgresException: ERROR: duplicate key value violates unique constraint "accounts_name_and_owner_firm_id_key"
DETAIL: Key (name, owner_firm_id)=(name222, 1) already exists.
/home/dmitry-trebushnikov/main/Sources/Trading/src/DbAccess/DatabaseTestFixture.cpp(187): last checkpoint
All you have to do is change impl/compiler_log_formatter.ipp (line 155):
if( !checkpoint_data.m_file_name.is_empty() ) {
// output << '\n'; // it was so
print_prefix( output, checkpoint_data.m_file_name, checkpoint_data.m_line_num );
BOOST_TEST_SCOPE_SETCOLOR( m_color_output, output, term_attr::BRIGHT, term_color::CYAN );
output << "last checkpoint";
if( !checkpoint_data.m_message.empty() )
output << ": " << checkpoint_data.m_message;
output << '\n'; // now it is
}
Have a good day:)
- Dominant language
- C++
- Stars
- 213
- Forks
- 149
- Avg merge
- 18h 17m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/test
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Conversion Warning with GCC15 when using operator<< within custom failure message and -WConversion Open
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·