Skip to content
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

GAIAPLAT-1195 : Following logical split, separating workload files from framework files. #863

Merged
merged 3 commits into from
Aug 26, 2021

Conversation

JackAtGaia
Copy link

@JackAtGaia JackAtGaia commented Aug 23, 2021

https://gaiaplatform.atlassian.net/browse/GAIAPLAT-1195

Following the first phase of this ticket, which performed a logical separation between the two parts, this phase specifically separates the files into those two parts.

Notes:

  • most of this PR are file moves from the /tests directory to the /tests/workloads/mink
  • lint.sh copied to /tests/workloads/mink as-is, version in /tests had c++ linting removed
  • suite.sh specifically set up to be hardwired to /workloads/mink for now
  • test.sh includes small change to set directory to the script's directory
  • mink.ruleset reset to previous version to test new changes independently of these changes

…ogical split, separating workload files from framework files.
Copy link
Contributor

@daxhaw daxhaw left a comment

Choose a reason for hiding this comment

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

I guess I'm not clear on the split here. Is this just the first step of a split where more will come later? Or is this a proposed split. Just seems like a lot of test harness stuff is still under the mink workload folder.

SCRIPTPATH="$( cd -- "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"
# shellcheck disable=SC1091 source=./properties.sh
source "$SCRIPTPATH/properties.sh"
#SCRIPTPATH="$( cd -- "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"
Copy link
Contributor

Choose a reason for hiding this comment

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

did you mean to leave a commented line in?

Copy link
Author

Choose a reason for hiding this comment

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

good catch

A.value = adjust_temperature(incubator.min_temp, incubator.max_temp, S.value, A.value);
A.timestamp = g_timestamp;
}
actuator.value = adjust_temperature(incubator.min_temp, incubator.max_temp, sensor.value, actuator.value);
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't recall our conversation, why not write it with the for loop?

Copy link
Author

Choose a reason for hiding this comment

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

I saw a couple of issues with this when I was testing it. One of my tasks for today is to see if those changes are introducing stable, and document them if they are.

@@ -0,0 +1,314 @@
#! /usr/bin/bash
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess I don't understand the split here. Shouldn't this be part of the framework, not the workload, and thus not under a mink subdirectory? Same with build.sh, install.sh, etc. Where the main framework just adds on command line arguments for the workload?

Copy link
Author

Choose a reason for hiding this comment

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

conversation to be had.

Copy link
Author

Choose a reason for hiding this comment

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

conversation had. will proceed along this path for now.

@@ -0,0 +1,161 @@
#! /usr/bin/python3

Copy link
Contributor

Choose a reason for hiding this comment

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

same question about this file. Isn't this framework and not specific to the mink workload? Except for parameters that I could see driving this generation?

@kenneth-gaia kenneth-gaia removed their request for review August 25, 2021 23:05
Copy link
Contributor

@daxhaw daxhaw left a comment

Choose a reason for hiding this comment

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

Approved with the understanding that this workload/framework split is a work in progress.

@JackAtGaia JackAtGaia merged commit 85078dc into master Aug 26, 2021
@JackAtGaia JackAtGaia deleted the jack/move-workload branch August 26, 2021 17:15
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