Skip to content

Conversation

@rcooke-warwick
Copy link
Contributor

…flashing

There is a large dump of errors sometimes when there is a connection fault while flashing the DUT via /flash on the worker. Attempt to catch it with this change to avoid large, useless crashdump in the logs

Change-type: patch

reject(error);
req.on('error', (error) => {
this.logger.log('Core side error when trying to send image to worker');
reject(new Error('Error while sending image to worker'));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we losing any valuable information here? Like the error code or something that could help with debugging?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The core dump usually doesn't give off any important information.
I would say if this is actually the source of the large core dump, then let's see if there any is any useful information that could be fetched from the error object?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rcooke-warwick can we still log error.message somewhere, assuming that's not where the dump is coming from? I don't like hiding all context from the error object.

…flashing

There is a large dump of errors sometimes when there is a connection fault while flashing the DUT via /flash on the worker. Attempt to catch it with this change to avoid large, useless crashdump in the logs

Change-type: patch
Signed-off-by: Ryan Cooke <[email protected]>
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.

3 participants