Conversation
* main: (66 commits) Remove network from sci (#1352) Updated Cloud Energy Relaxed test due to noise of host OS network management. See #1322 for details tcpdump will report errors for now instead of except Remaned wait_time to proper name idle_time Bump psutil from 7.0.0 to 7.1.0 (#1349) Refactor logs structure to json (#1341) Removed proxy passing into docker gunicorn container Changed jobs endpoint to deliver http 202 (fix): After moving to /lib folder the __main__ check was not relevant anymore. Checking for tty now which should not conflict when running in cluster mode fixes the problem with updates not being installed (#1346) Bump fastapi[standard] from 0.116.1 to 0.116.2 (#1342) Saves the existing config files on install (#1311) Fixes sudo bug when creating test env (#1310) Bump pydantic from 2.11.7 to 2.11.9 (#1340) Bump pytest-randomly from 4.0.0 to 4.0.1 (#1339) Bump actions/github-script from 7.0.1 to 8.0.0 in /.github/workflows (#1338) Bump actions/create-github-app-token in /.github/workflows (#1337) Added powermetrics carbon entries for config.js Added more key metrics to frontend display tests ...
* main: (36 commits) Remove the banner for the free version information on the unrestricted open source version Adding jobs and cluster_status_message demo entries to show that cluster mode is not active - Cluster Healthy message might lead to confusion otherwise Added nova coda editor to .gitignore email lib test code now also accepts file to read (fix): Email contains now chunked lines if lines > 1000 characters to cope with complaining SMTP servers Add container dependency collection (#1297) Updated Cloud Energy Bump fastapi[standard] from 0.117.1 to 0.118.0 (#1377) Bump pandas from 2.3.2 to 2.3.3 (#1378) (tests): Fix wording to new changed one Stdout and Stderr of subprocesses are now displayed better in logs (#1370) Fix double escaping in JS [skip ci] (#1376) Add debug outputs to investigate failing multi arch image test case (#1371) Cluster status is now also on request page [skip ci] (#1374) Double quoting can lead to escaping issues. No problem of having it not in quotes Fix checkboxes reset in user settings [skip ci] (#1366) Fix null byte handling in logs to prevent PostgreSQL errors (#1359) Bump uvicorn[standard] from 0.36.0 to 0.37.0 (#1365) Showing name and ID instead of only obfuscated info for user token (#1369) Bump pyyaml from 6.0.2 to 6.0.3 (#1368) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds bare metal tests for GMT when being tested inside DinD
The tests expectes the following named volumes on the system:
- gmt-tests-pip-cache:/root/.cache/pip/
- gmt-tests-apt-package-cache:/var/cache/apt/
- gmt-tests-apt-list-cache:/var/lib/apt/lists/
- gmt-tests-buildkit-cache:/root/.cache/buildkit-gmt/
Furthermore the the container must be orchestrated via
--network bridge.This is bc many DinD get resolver problems when too many network namespace nestings / islations happen.
On the cluster this means that the run must either be run with
--allow-unsafeor all parameters must be separately allowed.