| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
g_variant_string_array_has_string was partly aligned using tabs, which
only looks good when tab width is set to two spaces. Tabs have now been
replaced with spaces.
|
| |
|
|
|
| |
An implementation custom-tailored towards "{ias}" dictionaries is
sufficient for us.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed the requirement to restart the system for each test, instead
just restart the node startup controller for each test. The downside of
this is that the dlt.log file is not reset so may become very large.
Reduced the number of DLT log messages to compare against the output.
Instead, only the most relevant lines are included for each test.
Added separate test that the Node Startup Controller registers itself.
Rewrote the descriptions for each test case to be more readable.
Numbered each test case.
Spelling and grammar fixes.
|
| |
|
|
| |
The bus_name_id member is not longer used in this class.
|
| | |
|
| |
|
|
|
| |
Send NSM_ERROR_STATUS_ERROR rather than -1 back to the caller when an
unregister request could not be handled successfully.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
systemd uses SIGTERM to stop its units. We want to cleanly shut down
the NSC when receiving this signal. Part of that is to unregister all
shutdown consumers. If we don't do this, the NSM will later during its
shutdown phase call all shutdown consumers registered by the NSC. And
if the NSC was no longer running, this would cause the NSM to wait for a
timeout for every single one of these shutdown consumers. Obviously,
that is not desirable.
|
| |
|
|
|
|
|
|
| |
We use the "consumer" property of the ShutdownClient class to store a
proxy in the NSC code and a skeleton in the NSM dummy code. When
releasing the consumer in shutdown_client_finalize(), we may therefor
not cast to a ShutdownConsumerSkeleton unconditionally; otherwise
the NSM dummy will segfault when releasing ShutdownClient objects.
|
| |
|
|
|
|
| |
Fix in Test legacy app handling documentation the purpose, some
error logs and some commands.
Fix duplicate will in about.xml
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Changes the single instance of "we" in this file.
Minor grammatical fixes.
|
| |
|
|
|
|
| |
It now uses passive language throughout.
Other minor grammatical fixes
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit 5dfb47b1b80d3aa91b8493491050b9d70c31c57b.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The shutdown mode checker in the Node Startup Controller now uses the
same logging message as the legacy app handler helper binary.
The shutdown mode checker in the helper binary now uses the condition
statement from the Node Startup Controller
|
| |
|
|
|
|
| |
Added code to the register signal handler to refuse any register signal
which is not a combination of NSM_SHUTDOWN_TYPE_NORMAL and
NSM_SHUTDOWN_TYPE_FAST and log an error.
|
| |
|
|
|
| |
Replace the previous title by "Tests for legazy application handling".
Fix some paragraphs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Test titles are made more descriptive by including the name of the node
state which is being set.
A link is included to the enum which defines the NSMNodeState.
Tests are changed to always set the node state. This is done by
starting the unit twice in most cases. In addition, the less-important
lines in the DLT log output are no longer specified.
Capitalization in titles has been cleaned up somewhat.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the documentation for legacy app handling tests.
The following tests are provided:
1. Register a normal and a fast shutdown consumer.
- Check that node-startup-controller.service registers itself
as a shutdown consumer.
- Check that the registration for the shutdown consumer are ok.
- Check that in the process of shutting down the fast consumers
shutting down first and the normal consumers second.
- Check that the shutdown consumers are unregister as a shutdown
consumers when they have been shutting down.
- Check that node-startup-controller.service unregisters itself
as a shutdown consumer when it has been shutting down.
2. Register two normal shutdown consumers
- Check that in the process of shutting down the consumers are
shutting down in reverse order of registration.
3. Register a shutdown consumer twice within different modes and timeouts
- Check that the re-registration modify the final mode to a combination
of both modes (normal and fast) and the timeout has been set to the
last registration value of timeout.
- Check that in the process of shutting down the consumer is shutting down
for the both modes.
4. Register a shutdown consumer with invalid arguments
- Check that register a consumer without unit name fails.
- Check that register a consumer within mode 0 fails
- Check that register a consumer with a negative timeout fails.
|
| |
|
|
|
|
| |
Modify in the documentation for legacy app handler that timeout is a
non-mandatory legacy app handler argument and its default value is
1000 milliseconds.
|
| | |
|
| |
|
|
| |
Tests are restructured in the same way as the previous commit
|
| |
|
|
|
|
|
| |
Test cases are restructured into:
* Description
* Test Commands
* Desired behaviour and Output
|
| | |
|
| |
|
|
| |
Also fix a mistyped systemd command.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each test scenario (i.e. luc, legacy app, tsm) has been split into a
separate file.
Setup steps which have to be performed for every scenario are moved into
test-general-setup.xml
Cross-references are used so that the test overview links to each test
case, and the "Testing" page links to the general setup and also each
test.
test-example has been removed because it is no longer necessary.
|
| |
|
|
|
|
|
|
|
|
| |
The following test scenarios are added to the documentation:
* Registration of a simple dictionary
* Registration does not happen on an isolated RegisterWithLUC() call
* An isolated FinishLUCRegistration() call will not change the LUC
* Registration of a complex dictionary
* Registration can happen with a series of RegisterWithLUC() calls
* Repeated registration of an app changes the order in the LUC
|
