-
Notifications
You must be signed in to change notification settings - Fork 280
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
[Azure pipeline] Refresh configuration of rsyslogd using SIGHUP #1502
base: master
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
All passed, nice👍 |
Signed-off-by: Stephen Sun <[email protected]>
Signed-off-by: Stephen Sun <[email protected]>
fd0e0c6
to
ee87443
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @kcudnik @saiarcot895 |
seems like this will succeed |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
The latest rerun failed due to the following issue which is also observed previously [ OK ] VendorSaiTest.bulk_flow_entry (6 ms) |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
To overcome the rsyslog issue in azure pipeline test by refreshing rsyslogd configuration using SIGHUP instead of killing and restarting it.